gecko-dev/testing/mochitest
2007-07-18 21:59:26 -07:00
..
chrome Bug 370696. chrome mochitest. r=rcampbell 2007-02-20 01:56:30 +00:00
MochiKit Bug 359999. Add an enable-mochitest option. r=bsmedberg 2007-01-17 20:38:57 +00:00
static Remove extra whitespace at end of one line in test templates. rs=sayrer over IRC 2007-07-15 22:54:13 -07:00
tests Show diagnostics for todo tests. b=388690 r=sayrer 2007-07-18 21:59:26 -07:00
browser-harness.xul Bug 387455: adjust browser chrome test harness output (provide summary, don't fail if there are no tests), r=robcee 2007-07-12 07:29:33 -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 Slightly better handling of exceptions, especially parse errors. Bug 388248, r=gavin 2007-07-15 17:21:11 -07:00
gen_template.pl make gen_template.pl work from anywhere with FindBin 2006-11-08 19:19:19 +00:00
harness.xul css tweaks for harness pages. no bug 2007-04-22 12:34:39 -07:00
Makefile.in Bug 375469: new test framework to run tests in the browser window scope, r=sayrer 2007-07-09 09:24:15 -07:00
README.txt Bug 364043. Remove dependency on Python for HTTP server to serve mochitests. Patch by Jeff Walden <jwalden+bmo@mit.edu> and Robert Sayre <sayrer@gmail.com>. r=rcampbell 2007-01-26 18:44:58 +00:00
redirect.html Bug 370696. chrome mochitest. r=rcampbell 2007-02-20 01:56:30 +00:00
runtests.pl.in I think I figured out the problem with bug 384192; the code added to quit.js is also used in the browser tests, but it triggers an undefined-variable exception there, and I think the tests are getting killed by test timeout code that doesn't print a helpful 'tests timed out' message to give a little help determining the cause of the failure. We shall see... 2007-07-12 20:38:31 -07:00
server.js I think I figured out the problem with bug 384192; the code added to quit.js is also used in the browser tests, but it triggers an undefined-variable exception there, and I think the tests are getting killed by test timeout code that doesn't print a helpful 'tests timed out' message to give a little help determining the cause of the failure. We shall see... 2007-07-12 20:38:31 -07:00
server.py Add xul mime type to server.py 2006-10-28 21:46:33 +00: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>