This repository was archived by the owner on Mar 1, 2023. It is now read-only.
Smoke testing after deployment #270
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
added 3 commits
June 3, 2020 12:23
Signed-off-by: Marco Garofalo <[email protected]> Signed-off-by: Othman Alkhamra <[email protected]>
… how to run the smoke tests. Signed-off-by: Marco Garofalo <[email protected]> Signed-off-by: Othman Alkhamra <[email protected]>
Signed-off-by: Othman Alkhamra <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Create a smoke test (create retro, add items, archive retro) for Alex to check that his deployment has succeeded, as mentioned in #35.
This smoke test can be run with the new
smoke-test.shscript, which runs the test inside a new Docker container, so that Alex does not need to install any dependencies.Note: this test is intended to be run during the
test-packagescript, however this is waiting on some pipeline changes so it does not cause the final Travis step to run longer than 50 minutes and time out.When Alex has deployed an instance of postfacto but misconfigured it, this will enable him to quickly tell that the deployment has failed, rather than finding out from participants later.
I have reviewed the contributing guide
I have made this pull request to the
masterbranchI have run all the tests using
./test.sh.I have added the copyright headers to each new file added
I have given myself credit in the humans.txt file (assuming I want to)