fix(integ-runner): don't allow new legacy tests#20614
Merged
mergify[bot] merged 2 commits intoaws:mainfrom Jun 13, 2022
corymhall:corymhall/docs/integration-testing
Merged
fix(integ-runner): don't allow new legacy tests#20614mergify[bot] merged 2 commits intoaws:mainfrom corymhall:corymhall/docs/integration-testing
mergify[bot] merged 2 commits intoaws:mainfrom
corymhall:corymhall/docs/integration-testing
Conversation
All new integration tests that are created should use the new `IntegTest` construct in the [@aws-cdk/integ-tests](https://github.com/aws/aws-cdk/tree/main/packages/%40aws-cdk/integ-tests) module. We will eventually be migrating all of our tests to the new construct and removing the "legacy" mode, so this PR will fail any new test that is added that doesn't use the `IntegTest` construct. I've also renamed some of the `test-data` files so that they will not be picked up by the `integ-runner` if you execute it on the entire repo.
|
|
TheRealAmazonKendra
approved these changes
Jun 13, 2022
Contributor
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Collaborator
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Contributor
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
daschaa
pushed a commit
to daschaa/aws-cdk
that referenced
this pull request
Jul 9, 2022
All new integration tests that are created should use the new `IntegTest` construct in the [@aws-cdk/integ-tests](https://github.com/aws/aws-cdk/tree/main/packages/%40aws-cdk/integ-tests) module. We will eventually be migrating all of our tests to the new construct and removing the "legacy" mode, so this PR will fail any new test that is added that doesn't use the `IntegTest` construct. I've also renamed some of the `test-data` files so that they will not be picked up by the `integ-runner` if you execute it on the entire repo. ---- ### All Submissions: * [ ] Have you followed the guidelines in our [Contributing guide?](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) ### Adding new Unconventional Dependencies: * [ ] This PR adds new unconventional dependencies following the process described [here](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md/#adding-new-unconventional-dependencies) ### New Features * [ ] Have you added the new feature to an [integration test](https://github.com/aws/aws-cdk/blob/main/INTEGRATION_TESTS.md)? * [ ] Did you use `yarn integ` to deploy the infrastructure and generate the snapshot (i.e. `yarn integ` without `--dry-run`)? *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
All new integration tests that are created should use the new
IntegTestconstruct in the@aws-cdk/integ-tests
module.
We will eventually be migrating all of our tests to the new construct
and removing the "legacy" mode, so this PR will fail any new test that
is added that doesn't use the
IntegTestconstruct.I've also renamed some of the
test-datafiles so that they will not bepicked up by the
integ-runnerif you execute it on the entire repo.All Submissions:
Adding new Unconventional Dependencies:
New Features
yarn integto deploy the infrastructure and generate the snapshot (i.e.yarn integwithout--dry-run)?By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license