test: isolate tests from global config store

[thisislawatts]

Pull Request Submission Checklist

• Follows CONTRIBUTING guidelines
• Includes detailed description of changes
• Contains risk assessment (Low)
• Highlights breaking API changes (if applicable)
• Links to automated tests covering new functionality
• Includes manual testing instructions (if necessary)
• Updates relevant GitBook documentation (PR link: ___)

What does this PR do?

Introduces configuration isolation for E2E tests by creating a temporary Snyk configuration file for each test run. This ensures tests run with a clean configuration state and don't interfere with existing local configurations.

Key changes:

• Creates an isolated config file in OS temp directory if neither SNYK_CONFIG_FILE nor TEST_CONFIG_FILE is specified
• Adds logging of config file location via TEST_CONFIG_FILE for better debugging
• Implements cleanup of temporary files after test completion

Considered, but not implemented:

• Introducing unique configuration per CLI invocation. Seems like a reasonable next step but would be a more involved change.

Where should the reviewer start?

1. Review the Jest config changes in jest.config.js adding the new globalTeardown
2. Check the setup logic in test/setup.js for temporary config file creation
3. Examine the cleanup implementation in test/teardown.ts

How should this be manually tested?

1. Run E2E test suite without any config environment variables set
   • Verify a temporary config is created
   • Confirm the location is logged in test output
2. Run tests with SNYK_CONFIG_FILE set
   • Verify the specified config is used instead of creating a temporary one
3. Run tests with TEST_CONFIG_FILE set
   • Verify the specified config is used
4. After test completion, verify temporary config directories are cleaned up

[PeterSchafer]

Question: is this on purpose that the log says TEST_CONFIG_FILE and the env var used is SNYK_CONFIG_FILE?

[PeterSchafer]

Is TEST_CONFIG_FILE used somewhere?

[PeterSchafer]

I have never see SNYK_CONFIG_FILE before, are you sure it is supported in Golang and Typescript?