-
Notifications
You must be signed in to change notification settings - Fork 219
Improving stability and speed of intergration tests #384
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
Conversation
…e6 and node8 on different projects
| .then(() => { | ||
| console.log('All tests pass!'); | ||
| resp.status(200).send('PASS'); | ||
| resp.status(200).send('PASS \n'); |
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, this was bothering me :P
integration_test/run_tests.sh
Outdated
| deploy | ||
| waitForPropagation | ||
| run_tests | ||
| else |
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.
It took me some time to understand the difference between the two flows, but I understand why you needed to do them like this. Perhaps in the future we can keep the parallel deploys for node6 and node8 and find a way to have each test have a different name - that way we can keep the same flow for when the projects are the same (both would use the else part here).
Co-Authored-By: joehan <joehanley@google.com>
| deploy | ||
| waitForPropagation | ||
| run_all_tests | ||
| fi |
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
Description
Code sample
./run_tests.sh project1 project2 // runs node6 tests on project1 and node8 tests on project2, in parallel
./run_tests.sh projectId // runs node6 and node8 tests on projectId, in series