Add samples of how to test Graph QL Controller layer about graphql-spring-boot HOT 10 CLOSED

Here's my take on the above, in case anyone's interested: https://medium.com/@dSebastien/graphql-api-integration-tests-in-a-spring-boot-2-x-kotlin-application-5840d3c5d66f
HTH! :)

from graphql-spring-boot.

With a little help from the example of @dsebastien and the effort of @mxab we added the first version of graphql-spring-boot-starter-test that should help with writing your tests. See example-graphql-tools for example how to use it.

from graphql-spring-boot.

The issue seems to be that MockMvc isn't working with servlets. A workaround is to disable the servlet mapping and add spring wrapper controller like so:

@RestController
public class GQLController {

    @Autowired
    private GraphQLServlet graphQLServlet;

    @RequestMapping("graphql")
    public void graphql(HttpServletRequest request, HttpServletResponse response) throws Exception {
        graphQLServlet.service(request, response);
    }
 }

from graphql-spring-boot.

from graphql-spring-boot.

from graphql-spring-boot.

Would like that as well

from graphql-spring-boot.

That certainly helps, but I'm struggling specifically with the part how to ensure that not my entire context is auto loaded, and that only the relevant GraphQL part is loaded. How did you solve that? Do you include a specific configuration for your test, or do you exclude all the stuff you don't need?

The other stuff (Jpa, MVC controllers, etc) which I don't need for the GraphQL part takes too long to load for my tests, so I'm looking for a way to cut that load time considerably.

from graphql-spring-boot.

The maintenance of that is indeed a big downside.. I'll stick with the entire context for now, thanks!

from graphql-spring-boot.

How do you maintain the test queries? As escaped Strings in code or within separate files?
I'd like to put my test queries in dedicated (.graphql) files, for example:

mutation {
  createThing(name: "foo", description: "bar") {
    uuid,
    name,
    description
  }
}

And an easy way in Java to convert the above to what I actually need to send over the wire:

{
  "query": "mutation {\n  createThing(name: \"e\", description: \"cool\") {\n    uuid,\n    name,\n    description\n  }\n}",
  "variables": null
}

Has anyone done this yet? :)

from graphql-spring-boot.

I had an issue with using GraphQLTestTemplate provided with spring-boot-starter-test where my tests were @Transactional.

If I annotated tests with @Transactional and say I created a new record in a table (Obviously it wasn't committed yet as the test execution hasn't completed). Then I invoked a query using GraphQLTestTemplate, the resolvers were not able to see the created record. This is because GraphQLTestTemplate uses TestRestTemplate which invokes a http call, so when the execution comes to the resolvers a new Transaction is created, and this transaction doesn't have access to the entities created before.

If I get rid of @Transactional from test, then the test works fine, as the record is actually committed into the DB. But the side effect is that test records are now in the DB, and other integration tests running might break.

So, to support transactional integration testing I created a custom Tester here. You just need to autowire it into your test and use it. It usage is exactly the same as GraphQLTestTemplate, except it will ensure to maintain the Transactional context of test cases when annotated with @Transactional.

Although the issue is closed, I added this comment in case someone else comes looking for a similar requirement just like I did.

from graphql-spring-boot.