Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(integ-runner): test names change depending on the discovery direc…
…tory (#21093) The name of the test that is stored in the `integ.json` file for legacy test cases changes depending on what directory you run the test from. For example, if you were to run the below command from the root of the project the test name would be `@aws-cdk/aws-lambda/test/integ.assets.file` `yarn integ-runner --directory package/@aws-cdk/aws-lambda test/integ.assets.file.js` If you were to run this command from the `packages/@aws-cdk/aws-lambda` directory then the test name would be `integ.assets.file` `yarn integ integ.assets.file.js` This PR attempts to normalize the test name by using the name of the integration test file, minus the file extension. **Note, this only affects legacy test cases. The new style test cases have a different mechanism to generate a test name. I will create a follow up PR to update all of the `integ.json` files for all of the existing test cases to have the normalized name. ---- ### 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*
- Loading branch information