This PR enhances the Acceptance test workflow by enabling users to specify and run a single test within a Test Group.
This feature is particularly beneficial for executing long-running tests (such as cluster tests) during development, allowing developers to quickly test changes without waiting for the entire test suite/group to complete or tying up local machine resources.
Additionally, this helps in avoiding consuming more resources than strictly necessary for some feature/bug that we might be working on.
Link to any related issue(s):
Type of change:
[ ] Bug fix (non-breaking change which fixes an issue). Please, add the "bug" label to the PR.
[ ] New feature (non-breaking change which adds functionality). Please, add the "enhancement" label to the PR. A migration guide must be created or updated if the new feature will go in a major version.
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected). Please, add the "breaking change" label to the PR. A migration guide must be created or updated.
[ ] I have checked that this change does not generate any credentials and that they are NOT accidentally logged anywhere.
[ ] I have added tests that prove my fix is effective or that my feature works per HashiCorp requirements
[ ] I have added any necessary documentation (if appropriate)
[ ] I have run make fmt and formatted my code
[ ] If changes include deprecations or removals, I defined an isolated PR with a relevant title as it will be used in the auto-generated changelog.
[ ] If changes include removal or addition of 3rd party GitHub actions, I updated our internal document. Reach out to the APIx Integration slack channel to get access to the internal document.
Description
This PR enhances the Acceptance test workflow by enabling users to specify and run a single test within a Test Group.
This feature is particularly beneficial for executing long-running tests (such as cluster tests) during development, allowing developers to quickly test changes without waiting for the entire test suite/group to complete or tying up local machine resources.
Additionally, this helps in avoiding consuming more resources than strictly necessary for some feature/bug that we might be working on.
Link to any related issue(s):
Type of change:
Required Checklist:
Further comments
Test run for below workflow: https://github.com/mongodb/terraform-provider-mongodbatlas/actions/runs/9567292550![Screenshot 2024-06-18 at 15 45 06](https://github.com/mongodb/terraform-provider-mongodbatlas/assets/122359335/6d4a69e4-bb4e-44f4-b9df-a1e3cc4f35cb)