mozilla

Compare Revisions

Mochitest

Change Revisions

Revision 485701:

Revision 485701 by Markh on

Revision 499585:

Revision 499585 by Jonathan_Watt on

Title:
Mochitest
Mochitest
Slug:
Mochitest
Mochitest
Tags:
"Developing Mozilla", "Automated testing"
"Developing Mozilla", "Automated testing"
Content:

Revision 485701
Revision 499585
n96    <h4 id="Running_mochitests_under_Electrolysis_(e10s)">n96    <h4 id="Running_mochitests_under_Electrolysis_(e10s)_for_Fenn
 >ec">
n114    <h4>n114    <h4 id="Running_mochitests_under_Electrolysis_(e10s)_for_Desk
 >top_builds.">
t310      Makefile changest310      mochitest.ini changes
311    </h4>
312    <p>311    </h4>
313      To tell the build system about your new test you need to ad
>d the name of your test file to <code>MOCHITEST_FILES</code> in t 
>he test directory's <code>Makefile.in</code>. 
314    </p>312    <p>
315    <p>313      To tell the build system about your new test you need to ad
 >d the name of the test file to the mochitest.ini file in the test
 >'s directory. <a href="/en-US/docs/">The mochitest.ini file forma
 >t is documented here</a>.
316      If your test spans multiple files, only name the main one "
>test_...". This is the one that will show up in the list of testc 
>ases to run. The other files should have some other name, but mus 
>t still be added to the <code>MOCHITEST_FILES</code> in <code>Mak 
>efile.in</code>. 
317    </p>
318    <p>
319      Keep in mind that if you're adding chrome tests, you'll nee
>d to add the test to <code>MOCHITEST_CHROME_FILES</code> instead. 

Back to History