[povilasjurcys]

What's the reason for this feature?

Currently, the RSpec controller helpers keep the request private, so a matcher judging response can't see the context the action ran with. rspec_extra_matchers' be_successful_graphql_request needs it to call model fields that read graphql_context, as GraphqlRails does at runtime.

This PR adds response.context, which returns the request's context (the hash-like FakeContext, not a GraphQL::Query::Context).

Reviewers should know:

• FakeContext delegates only [], []=, to_h, key? and fetch. Decorators that call graphql_context&.dig(...) will raise once the matcher passes this context. That is still open: adding dig to FakeContext here is the likely fix.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.17%. Comparing base (2f27ea3) to head (497b80e).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #316   +/-   ##
=======================================
  Coverage   98.17%   98.17%           
=======================================
  Files          68       68           
  Lines        1920     1922    +2     
=======================================
+ Hits         1885     1887    +2     
  Misses         35       35           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.