-
Notifications
You must be signed in to change notification settings - Fork 178
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
chore: Single Github Action for migration and acceptance tests #2156
Conversation
@@ -103,13 +107,30 @@ env: | |||
TF_ACC: 1 | |||
TF_LOG: ${{ vars.LOG_LEVEL }} | |||
ACCTEST_TIMEOUT: ${{ vars.ACCTEST_TIMEOUT }} | |||
ACCTEST_REGEX_RUN: "^TestAcc" | |||
# Only Migration tests are run when testing a specific previous provider version instead of the latest one | |||
ACCTEST_REGEX_RUN: ${{ inputs.provider_version == '' && '^Test(Acc|Mig)' || '^TestMig' }} |
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.
@EspenAlbert thanks for your suggestion!
@@ -57,13 +59,14 @@ func TestMigNetworkContainer_basicAzure(t *testing.T) { | |||
|
|||
func TestMigNetworkContainer_basicGCP(t *testing.T) { | |||
var ( | |||
projectID = acc.ProjectIDExecution(t) // No mig.ProjectIDGlobal because network container |
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.
[q] Now that migration and acceptance test run in the same package execution, is there value in preserving mig.ProjectIDGlobal
? My understanding is that ProjectIDExecution
could be used if the resource package is already using it for acceptance tests.
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.
you read my mind :-) i was planning a follow-up PR to delete mig.ProjectIDGlobal
uses: ./.github/workflows/acceptance-tests.yml | ||
with: | ||
terraform_version: ${{ matrix.terraform_version }} | ||
provider_version: ${{ matrix.provider_version }} | ||
atlas_cloud_env: ${{ inputs.atlas_cloud_env }} |
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.
[q] If the test suite is executed with a list of provider versions (for migration tests), acceptance tests would only be run if the value "" is also included right?
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.
correct
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 👍
🤔 would there be a way of sorting the jobs.change-detection.steps.filter
in acceptance-tests-runner.yml
?
Did a little smoke test to see if any paths are lost between the migration-tests.yml
and acceptance-tests-runner.yml
and it looked good, did you double check?
@EspenAlbert I double-checked but I agree. I also wanted to do a follow-up PR doing that and also trying to simplify, so for instance we don't need to define twice things like:
|
Description
Single Github Action for migration and acceptance tests.
Fixes network and project test groups so acc and mig tests can run together.
Link to any related issue(s): CLOUDP-241162
Type of change:
Required Checklist:
Further comments