Catching GraphQLLocatedError for tests

Is your feature request related to a problem? Please describe. No, question about doing a particular thing

Describe the solution you’d like I’d like to know the way to catch GraphQLLocatedError, or a way to assertRaises them.

I’ve tried :

• try…except way :

try:
    response = self.client.execute(query, variables)
except GraphQLLocatedError:
    self.fail(...)

• with self.assertRaises(…) way :

with self.assertRaises(GraphQLLocatedError):
    response = self.client.execute(query, variables)

But none of these work. How can I do this ?

[zbyte64]

In the past I have used the following class to get stack traces of exceptions:

from graphql.execution import ExecutionContext

class DebugExecutionContext(ExecutionContext):
        def handle_field_error(
            self, raw_error: Exception, field_nodes, path, return_type,
        ) -> None:
            import traceback            
            traceback.print_exception(
                type(raw_error), raw_error, raw_error.__traceback__
            )
            return super().handle_field_error(raw_error, field_nodes, path, return_type)

Then when I setup my view in the urls.py I pass it as an option:

GraphQLView.as_view(execution_context_class=DebugExectionContext)

Kind of lame that this method still requires patching the urlconf for use in tests: https://pytest-django.readthedocs.io/en/latest/helpers.html#pytest-mark-urls-override-the-urlconf

[kubami]

The above error is caused by hasattr check in .as_view, as it is not aware that the GraphQLView has that attribute. The below PR fixes that.