You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello! I'm wondering if there is a decent guide on integration testing with this library? I think my confusion is fairly well expressed in this issue: #273. Fragment masking should (I think) mean that a parent component doesn't have to know anything about the data requirements of its children. But that ends when you try and test a component that has anything more than a few nested fragments. It seems like the direction the replies to that issue are pointing to is end to end testing against a real GraphQL server. I feel like this could handle some of the scenarios I am thinking about, but I still feel like I am missing something for complex components that might get shared between multiple applications (thinking of a package in a monorepo, for example).
Is there a different way I should try to structure my application when using this library that will make it easier to integration test? Any ideas/suggestions would be appreciated. Thanks!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello! I'm wondering if there is a decent guide on integration testing with this library? I think my confusion is fairly well expressed in this issue: #273. Fragment masking should (I think) mean that a parent component doesn't have to know anything about the data requirements of its children. But that ends when you try and test a component that has anything more than a few nested fragments. It seems like the direction the replies to that issue are pointing to is end to end testing against a real GraphQL server. I feel like this could handle some of the scenarios I am thinking about, but I still feel like I am missing something for complex components that might get shared between multiple applications (thinking of a package in a monorepo, for example).
Is there a different way I should try to structure my application when using this library that will make it easier to integration test? Any ideas/suggestions would be appreciated. Thanks!
Beta Was this translation helpful? Give feedback.
All reactions