GitAuto: Add an integration test for get_graphql_client in services/github/graphql_client.py

[gitauto-for-dev]

Resolves #560

Why is this feature needed?

To ensure the reliability of our GitHub GraphQL client, this integration test verifies that the client created by get_graphql_client in services/github/graphql_client.py can successfully execute a simple GraphQL query and retrieve accurate repository information.

What and how are we changing? Why this approach?

We are adding an integration test in tests/integration/test_graphql_client.py. The new test does the following:

• Creates a GitHub GraphQL client using a provided token.
• Prepares a basic GraphQL query to retrieve repository details, including the repository name and owner login.
• Executes the query and checks that the response contains the expected repository details.

This approach directly tests the functionality of the GraphQL client in an integration scenario, ensuring that it interacts properly with the GitHub GraphQL API and that no regressions have been introduced.

What actions are required from users?

Users must ensure that:

• A valid GitHub token (TOKEN) is provided.
• The constants for OWNER and REPO are correctly configured to match an accessible repository.
• The environment is correctly set up for integration testing against the GitHub API.

How does it work? (Technical details)

• The test invokes get_graphql_client with a predefined TOKEN to create the client.
• It then defines a simple GraphQL query that takes "owner" and "repo" as variables and requests the repository's name and owner's login.
• The test executes the query using the client's execute method and asserts that the response includes the "repository" key with the expected repository name.
• This verifies the basic functionality of our GraphQL client and its ability to communicate with the GitHub API.

Is it backwards compatible?

Yes. This change only introduces a new integration test and does not affect any existing functionality, making it fully backwards compatible.

Any other considerations?

Keep in mind that this integration test relies on external API calls to GitHub, so factors like network availability and the proper configuration of access tokens are necessary for the test to pass. In future iterations, we might consider adding more tests to cover additional scenarios or handling potential failures more gracefully.

git fetch origin
git checkout gitauto-wes/issue-560-20250211-125544
git pull origin gitauto-wes/issue-560-20250211-125544

[gitauto-for-dev]

Committed the Check Run build error fix! Running it again...