Closed
Bug 1359585
Opened 8 years ago
Closed 8 years ago
Run tecken systemtests just prior to deployment
Categories
(Socorro :: Symbols, task)
Socorro
Symbols
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: peterbe, Unassigned)
References
Details
Reporter | ||
Comment 1•8 years ago
|
||
Do you think you can incorporate this into the build/deployment automation?
When you run `docker-compose run systemtest tests/systemtest/run_tests.sh` locally, it uses docker to run this. And then it's able to re-use the Python environment inside the docker image. If you run that `tests/systemtest/run_tests.sh` outside, it might not work because you need to install a couple more dependencies. But I can code around that if that's how you run things.
Basically, help me help you help me :)
Flags: needinfo?(miles)
Comment 2•8 years ago
|
||
The systemtest runs in dev, properly sends an email notification with information about test failures, etc. When we move to running tecken in stage the systemtest will be run by Jenkins sshing into the boxes rather than on puppet cron.
Flags: needinfo?(miles)
Reporter | ||
Comment 3•8 years ago
|
||
Is that still working and being used during deployments? On dev *and* stage?
For the record, running the systemtests locally is currently broken. It's docker related and something to do with the web app not being reachable at all.
Flags: needinfo?(miles)
Comment 4•8 years ago
|
||
No, it doesn't happen. The systemtest is broken in those environments as well, I think for the same reason.
Flags: needinfo?(miles)
Comment 5•8 years ago
|
||
This + logging are todo for tecken but non-blocking to load-testing.
Reporter | ||
Comment 6•8 years ago
|
||
Pretty sure this is in place already. At least in Dev and Stage.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•