gecko/testing/mochitest
2008-04-10 22:58:04 -07:00
..
chrome Bug 389793 Firefox build failed on OpenSolaris without --disable-mochitest r=benjamin a=dsicore 2007-08-05 20:22:32 -07:00
MochiKit Fix detection of whether we're in HTML. Bug 386526, r=sayrer 2007-09-19 18:26:14 -07:00
ssltunnel fix linebreaks in Makefile.in from bug 426867 to unbreak OS/2 build (test only code) 2008-04-10 22:58:04 -07:00
static Bug 423787 - "XUL test template has typo in comment" [p=manish@flock.com (Manish Singh) r=sayrer] 2008-03-28 23:45:45 -07:00
tests Bug 416074: TestRunner attempts to log after closing the log, r+a=sayrer 2008-02-06 23:18:45 -08:00
browser-harness.xul bug 390539: honor the --test-path option for browser chrome tests as well; r=gavin 2007-09-27 15:11:05 -07:00
browser-test-overlay.xul Bug 375469: new test framework to run tests in the browser window scope, r=sayrer 2007-07-09 09:24:15 -07:00
browser-test.js bug 419826 - Make browser mochitests run on SeaMonkey, r=gavin 2008-02-28 13:36:30 -08:00
gen_template.pl Free the (distributed) Lizard! Automatic merge from CVS: Module mozilla: tag HG_REPO_INITIAL_IMPORT at 22 Mar 2007 10:30 PDT, 2007-03-22 10:30:00 -07:00
harness-a11y.xul Bug 423035: can't run single chrome/a11y test automatically; r=Waldo 2008-03-18 12:57:22 -07:00
harness-overlay.xul Bug 423035: can't run single chrome/a11y test automatically; r=Waldo 2008-03-18 12:57:22 -07:00
harness.xul Bug 423035: can't run single chrome/a11y test automatically; r=Waldo 2008-03-18 12:57:22 -07:00
Makefile.in bug 426867 - ssl proxy for mochitest. r=sayrer/kaie (test only code) 2008-04-09 08:30:54 -07:00
README.txt Free the (distributed) Lizard! Automatic merge from CVS: Module mozilla: tag HG_REPO_INITIAL_IMPORT at 22 Mar 2007 10:30 PDT, 2007-03-22 10:30:00 -07:00
redirect-a11y.html Bug 416553 - option to run accessibility tests, r=rcampbell 2008-02-14 02:32:21 -08:00
redirect.html Bug 416553 - option to run accessibility tests, r=rcampbell 2008-02-14 02:32:21 -08:00
redirect.js Bug 416553 - option to run accessibility tests, r=rcampbell 2008-02-14 02:32:21 -08:00
runtests.pl.in backing out bug 424501 to verify it doesn't /cause/ firefox to crash 2008-03-22 17:04:36 -07:00
runtests.py.in Bug 418009 - Make runtests.py properly handle stdout for both the server and the application processes, rather than just sitting on the server output and hoping it doesn't grow 'too large'. This may fix some of the problems that were plaguing the PGO box that was using runtests.py a few days ago, and it should fix hangs numerous people have seen running Mochitests lately, where the server process decides to spew gobs of output about stuff being leaked. r=robcee 2008-04-07 22:18:45 -07:00
server.js Bug 416390, context-click on listbox does not select item, also increases size of test frame, r=neil 2008-04-01 14:21:54 -07:00

 ----------------
 mochitest README
 ----------------

Steps to get started:

 1.) Run the runtests.pl script to start the server.
 
     Currently, the test script automatically determines the location
     of *Firefox*.

 2.) gen_template.pl will generate test templates for HTML, XUL, and XHTML.
     Read the comment at the top of the file for usage instructions.

 3.) Write a test.


Example test:

<!DOCTYPE HTML>
<html>
<!--
https://bugzilla.mozilla.org/show_bug.cgi?id=345656
-->
<head>
  <title>Test for Bug 345656</title>
  <script type="text/javascript" src="/MochiKit/MochiKit.js"></script>
  <script type="text/javascript" src="/tests/SimpleTest/SimpleTest.js"></script>        
  <link rel="stylesheet" type="text/css" href="/tests/SimpleTest/test.css" />
</head>
<body>
<p id="display"></p>
<div id="content" style="display: none">
  
</div>
<pre id="test">
<script class="testbody" type="text/javascript">

/** Test for Bug 345656 **/
//
//add information to show on the test page
//
$("display").innerHTML = "doing stuff...";

//
// The '$' is function is shorthand for getElementById. This is the same thing:
//
document.getElementById("display").innerHTML = "doing stuff...";

//
// you can add content that you don't want to clutter 
// the display to the content div.
//
// You can write directly, or you can use MochiKit functions
// to do it in JS like this:
//
appendChildNodes($("content"),
                 DIV({class: "qux"},
                     SPAN({id: "span42"}, "content"))
                 );

//
// the ok() function is like assert
//
ok(true, "checking to see if true is true);

//
// this will fail
//
ok(1==2, "1 equals 2?");


//
// this will be marked as a todo.
// When we fix 1 so it equals 2, we'll need to change this 
// function to ok() or is().
//
todo(1==2, "1 equals 2?");

//
// is() takes two args
//
myVar = "foo";
is(myVar, "foo", "checking to see if myVar is 'foo'");

//
// Tests can run in event handlers.
// Call this to tell SimpleTest to wait for SimpleTest.finish() 
//
SimpleTest.waitForExplicitFinish();

//
// event handler:
//
function event_fired(ev) {
  is(ev.newValue, "width: auto;", "DOMAttrModified event reports correct newValue");
  SimpleTest.finish(); // trigger the end of our test sequence
}

//
// Hook up the event. Mochikit.Signal has many conveniences for this, if you want.
//
$("content").addEventListener("DOMAttrModified", event_fired, false);

//
// Fire the event.
//
$("content").style.width = "auto";

</script>
</pre>
</body>
</html>