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)

enhancement
Not set
normal

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.
Encrypted sauce credentials: secure: "SnWizKd9zRohcjRO7Dpslz2VHLo3pYruz5p1KWcHDa3ttVxMXGhNz1jBUD/Lazn1uifqSoI8o8nMC503VXc+hu9Gq33wDjjoQRAU4srz13Acr6uRe7mNnGt3P9dKqODucMMqn0FvcZv+7z9vD73KNWLYk8n70Bd3+Wsmcre4kyE=" secure: "fR75lloHnd0VT1pWuFy0Z4eExjb4/q+SPoC77xWiPXLmojsPUQYEZaGQCB4EPGioIHI4TWxM5dBkwyNrp+rOjJaWeZv3IIhpQshAtdbcckyET3Ang4CtJK/900SoS1ZyDag1kKg28vXYvJKyxcx6p0uUI+E1exTtCydjyLNp8rk="
Severity: normal → enhancement
Keywords: in-triage
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
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
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
See Also: → 1314708
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.