only recently explored and implemented:
executions within GraphQL RootQueryType keys with resolve functions, invoked with clientside async fetching.
given this fact, the advantage of HTTP in this case is that its easier to dig into the API with console.logs()
one could do the same in POSTMAN, but with GraphQL needing tighter definition over consumable api endpoints,
overfetching of data that graphQL solves that it requires no specificity in its endpoint, and that the root object can be referenced
bookmarking more careful consideration of whether to use graphQL to test further use cases of puppeteer or HTTP.
only recently explored and implemented: executions within GraphQL RootQueryType keys with resolve functions, invoked with clientside async fetching.
given this fact, the advantage of HTTP in this case is that its easier to dig into the API with console.logs() one could do the same in POSTMAN, but with GraphQL needing tighter definition over consumable api endpoints,
overfetching of data that graphQL solves that it requires no specificity in its endpoint, and that the root object can be referenced bookmarking more careful consideration of whether to use graphQL to test further use cases of puppeteer or HTTP.
http for reason above