Reduce smoke test suite size #2182
Merged
Conversation
This file contains 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
The smoke tests are taking too long, 5m on linux and 10m+ on windows on our CI servers. The goal for the smoke tests is <3m so that it's easy to run and vet that you didn't completely break porter. I've moved some of the smoke tests into the integration test suite so that we are only focusing on the most important checks in the smoke test suite. Signed-off-by: Carolyn Van Slyck <me@carolynvanslyck.com>
|
/azp run |
|
Azure Pipelines successfully started running 4 pipeline(s). |
VinozzZ
approved these changes
Jun 21, 2022
|
This brought the windows smoke test run down from 10m to ~4m. The integration tests are taking 20m and will need to be looked at for redundant test cases and optimizations so that it runs faster (usually by stacking more assertions onto a single bundle run). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The smoke tests are taking too long, 5m on linux and 10m+ on windows on our CI servers. The goal for the smoke tests is <3m so that it's easy to run and vet that you didn't completely break porter.
I've moved some of the smoke tests into the integration test suite so that we are only focusing on the most important checks in the smoke test suite.