We should have some docs that explain how to run our Django testsuite and our Selenium test suite (mcom-tests). Without those tests passing, a commit should not be pushed to production.
(In reply to Anthony Ricaud (:rik) from comment #0) > We should have some docs that explain how to run our Django testsuite and > our Selenium test suite (mcom-tests). > > Without those tests passing, a commit should not be pushed to production. The selenium mcom-tests has an up to date README file
This is about writing this into http://bedrock.readthedocs.org/ so people know about mcom-tests. Also, the README on mcom-tests is out-of-date. You don't need a Java Runtime installed to run those tests.
I did not get the time to create those properly. So just putting some content here for now: We have two set of automated tests: - Embedded inside the Bedrock codebase. Run them with ./manage.py test - Selenium tests + requests based: https://github.com/mozilla/mcom-tests. Run them with: - pip install -r requirements/requirements.txt - py.test --driver=firefox - py.test --driver=firefox -k redirect to filter (see -k help manual for what it does) - For local testing, you can change the server they run on inside mozwebqa.cfg - those tests are important because of our weird Apache setup Jenkins instances: https://ci.mozilla.org/job/bedrock/ for Django tests http://qa-selenium.mv.mozilla.com:8080/job/mozilla.com.prod/ for mcom-tests http://qa-selenium.mv.mozilla.com:8080/job/mozilla.com.trunk/ for mcom-tests IRC bots to request builds: jenkins and qatestbot in #www
Component: www.mozilla.org → General
Product: Websites → www.mozilla.org
This is an old bug - closing as we now have consolidated Selenium tests in the bedrock repo which have new documentation: http://bedrock.readthedocs.org/en/latest/testing.html
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.