Closed
Bug 1197858
Opened 10 years ago
Closed 8 years ago
Run intern test suite during Travis builds
Categories
(developer.mozilla.org Graveyard :: General, enhancement)
developer.mozilla.org Graveyard
General
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: groovecoder, Unassigned)
References
Details
(Keywords: in-triage)
When we make code changes, we want to see intern test results in the Travis builds, so we can prevent ourselves merging code into master that breaks the functionality covered by Intern.
http://docs.travis-ci.com/user/gui-and-headless-browsers/ has some ideas including Sauce Labs (bug 1186899), or xvfb.
Comment 1•10 years ago
|
||
Encrypted sauce credentials:
secure: "SnWizKd9zRohcjRO7Dpslz2VHLo3pYruz5p1KWcHDa3ttVxMXGhNz1jBUD/Lazn1uifqSoI8o8nMC503VXc+hu9Gq33wDjjoQRAU4srz13Acr6uRe7mNnGt3P9dKqODucMMqn0FvcZv+7z9vD73KNWLYk8n70Bd3+Wsmcre4kyE="
secure: "fR75lloHnd0VT1pWuFy0Z4eExjb4/q+SPoC77xWiPXLmojsPUQYEZaGQCB4EPGioIHI4TWxM5dBkwyNrp+rOjJaWeZv3IIhpQshAtdbcckyET3Ang4CtJK/900SoS1ZyDag1kKg28vXYvJKyxcx6p0uUI+E1exTtCydjyLNp8rk="
Comment 2•10 years ago
|
||
Commits pushed to master at https://github.com/mozilla/kuma
https://github.com/mozilla/kuma/commit/44ee7b476f6703b3f4d5b8e5bd20ae876e7c3799
bug 1197858 - Upgrade intern to 3.0.3
https://github.com/mozilla/kuma/commit/761c8fcddddc26470cac16ddd14d16604256c631
bug 1197858 - update intern-sauce-labs config
https://github.com/mozilla/kuma/commit/3bc31318c425379a236cefde9b02f441ad75eb31
bug 1197858 - add browserstack config
https://github.com/mozilla/kuma/commit/bb8d135a272f71b2fc4c0a5567ce2b964d522d1b
bug 1197858 - Update base tunnelOptions settings, add larger async timeout
https://github.com/mozilla/kuma/commit/341be74ff2b31fc3dd62fa65058dd9ec6f1d4439
bug 1197858 - isolate environments and update concurrency
https://github.com/mozilla/kuma/commit/868fa3699f78a9502679890d3b4417352e6c9c5f
Merge pull request #3498 from mozilla/upgrade-intern
bug 1197858 - Upgrade intern to 3.0.3
Comment 3•10 years ago
|
||
Commits pushed to master at https://github.com/mozilla/kuma
https://github.com/mozilla/kuma/commit/897162c3accbf7099945f100095e034fa07419c6
bug 1197858 - Set larger test timeouts for remote runners
https://github.com/mozilla/kuma/commit/2d5b579c63e37e2d4b69d884fda5945bd689303e
Merge pull request #3551 from mozilla/1197858-test-timeout
bug 1197858 - Set larger test timeouts for remote runners
Comment 4•8 years ago
|
||
Marking as Incomplete. Things have changed in two years...
We're using Python + Selenium rather than Intern / JS + Selenium (bug 1314708)
We run the functional tests from Jenkins [1] when SCL3 staging is updated. This requires merging to the stage-integration-tests branch [2]. We can run the integration tests by creating a branch in the main repo, along with a branch-specific Jenkinsfile [3], so we can test UI changes and new functional tests in Jenkins.
We now have the infrastructure to create a ephemeral deployments based on PRs, and could run the tests against them. However, we still want a sanity check on PR code before running user-submitted code in our infrastructure. We're also working on the reliability of these tests. Functional test failures are as often due to bad tests rather than broken functionality.
The current state is good enough for now, and the next step is automating functional tests as part of deployment pipelines, not as part of the regular PR process.
[1] https://ci.us-west.moz.works/view/MDN/job/mdn_multibranch_pipeline/job/stage-integration-tests/
[2] https://kuma.readthedocs.io/en/latest/deploy-scl3.html
[3] https://kuma.readthedocs.io/en/latest/tests-ui.html
Updated•5 years ago
|
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•