-
Notifications
You must be signed in to change notification settings - Fork 207
chore: Run Go tests using specific packages #2014
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice improvement!!
TEST_REGEX: "^TestAccConfig" | ||
ACCTEST_PACKAGES: | | ||
./internal/service/alertconfiguration | ||
./internal/service/atlasuser | ||
./internal/service/databaseuser | ||
./internal/service/projectapikey |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
like how each test group now defines explicitly which resources are included without relying on the naming indirection. Nice side benefit from the package restructure some months back.
This looks more neat! |
Description
Run Go tests using specific packages.
This allows to have a cleaner test output log and better performance as only the needed packages are run.
It also reduces the risk of skipping tests in CI because bad test names.
Link to any related issue(s): CLOUDP-237342
Type of change:
Required Checklist:
Further comments
In future PRs there might be some opportunities to reduce duplication, e.g. generic config includes:
Example of new test log for assume-role (much less verbose):
Example of existing log: