GraphQL generally makes frontend development easier, but dropping a query into a previously dumb component can suddenly make its tests and stories more complicated. Chang walks us through the current solution for mocking query responses and why it can be rather cumbersome, then show how to build an alternative uses automocked responses that should reduce maintenance burden (but has its own shortcomings), and finally what a (yet undetermined) ideal solution might look like.