Apps/QA/MochiTest: Difference between revisions
(Created page with "= Get Mochitests Running = == Purpose == Gather enough information to get our html / js test suite for the javascript api to get it working for mozilla central. == First St...") |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 24: | Line 24: | ||
Server Locations: | Server Locations: | ||
http://mxr.mozilla.org/mozilla-central/source/build/pgo/server-locations.txt | http://mxr.mozilla.org/mozilla-central/source/build/pgo/server-locations.txt | ||
Basically the app project allows one origin per app, node js served up the apps on different ports as a way around this problem. | |||
In mochitest, i just tied the app origins to the the server-locations list that mochitest automatically spoofs. | |||
Filed the preliminary bug with the attached output | |||
https://bugzilla.mozilla.org/show_bug.cgi?id=731134 | |||
Latest revision as of 19:45, 28 February 2012
Get Mochitests Running
Purpose
Gather enough information to get our html / js test suite for the javascript api to get it working for mozilla central.
First Step
Github repo:
https://github.com/dclarke/webapps-mochitest/
Grab the github repo:
Second Step
Branch: entire_suite
This is where i am attempting to bridge the pure html / js test suite with what is mochi test. The advantage here is that for each new test that is added to one suite, it is comparatively less work to add tests if you are working on webapps, and you are familiar with doctestjs.
Problems I have found:
Server Locations:
http://mxr.mozilla.org/mozilla-central/source/build/pgo/server-locations.txt
Basically the app project allows one origin per app, node js served up the apps on different ports as a way around this problem. In mochitest, i just tied the app origins to the the server-locations list that mochitest automatically spoofs.
Filed the preliminary bug with the attached output
https://bugzilla.mozilla.org/show_bug.cgi?id=731134