Skip to content
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

Optimize integration test speed #93

Open
VinozzZ opened this issue Mar 30, 2022 · 1 comment
Open

Optimize integration test speed #93

VinozzZ opened this issue Mar 30, 2022 · 1 comment
Labels
2 - 🍕 Pizza should be eaten daily self care 💅🏽 Tasks that help keep Porter running smoothly

Comments

@VinozzZ
Copy link
Contributor

VinozzZ commented Mar 30, 2022

Currently, when an integration test runs, it has set up and tear down so it's slow.
We would like to find a way to optimize the setup and reduce the tests run time

@carolynvs carolynvs added 2 - 🍕 Pizza should be eaten daily self care 💅🏽 Tasks that help keep Porter running smoothly labels Apr 1, 2022
@carolynvs carolynvs moved this from Inbox to Backlog in Porter and Mixins Apr 1, 2022
@carolynvs carolynvs moved this from Backlog to Inbox in Porter and Mixins Apr 1, 2022
@carolynvs
Copy link
Member

In general a way to speed up integration tests is to limit the number of tests and set up and verify more scenarios within a single test. This limits the number of times you pay the cost for setup/teardown.

The tests do get longer, and a good way to group them is by "workflow", chaining together multiple related tasks that someone would usually do. Here is an example from Porter's smoke tests: https://github.com/getporter/porter/blob/release/v1/tests/smoke/desiredstate_test.go

@carolynvs carolynvs moved this from Inbox to Backlog in Porter and Mixins Apr 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 - 🍕 Pizza should be eaten daily self care 💅🏽 Tasks that help keep Porter running smoothly
Projects
Porter and Mixins
  
Backlog
Development

No branches or pull requests

2 participants