2006-10-25 20:40:15 +00:00
|
|
|
----------------
|
|
|
|
|
mochitest README
|
|
|
|
|
----------------
|
|
|
|
|
|
|
|
|
|
Steps to get started:
|
|
|
|
|
|
2006-10-25 20:47:12 +00:00
|
|
|
1.) Right now, you will need to edit some constants in runtests.pl. Windows
|
|
|
|
|
is not yet supported.
|
2006-10-25 20:40:15 +00:00
|
|
|
|
|
|
|
|
2.) Start the python server in a separate console:
|
|
|
|
|
|
|
|
|
|
%> python server.py
|
|
|
|
|
|
|
|
|
|
It runs at http://localhost:8888/. Control-C will kill it. We are looking
|
|
|
|
|
at other server options, because we don't want to require python.
|
|
|
|
|
|
|
|
|
|
3.) New test cases can be added to the tests/ directory. We are working on
|
|
|
|
|
easy test navigation and automated test addition.
|
|
|
|
|
|
|
|
|
|
4.) gen_template.pl takes a bug number as its only argument and outputs a
|
|
|
|
|
test template to stdout.
|
|
|
|
|
|
|
|
|
|
5.) Write a test.
|
|
|
|
|
|
|
|
|
|
|
2006-10-26 20:03:27 +00:00
|
|
|
Checkin rules:
|
2006-10-25 20:40:15 +00:00
|
|
|
|
|
|
|
|
1.) Any module owner/peer/member should feel free to check in a test case.
|
|
|
|
|
|
2006-10-26 20:03:27 +00:00
|
|
|
2.) Tests should always be passing, and failing tests will make the tree
|
|
|
|
|
turn orange (very soon). If you have tests that you know are going to
|
|
|
|
|
fail, use the todo() function.
|
|
|
|
|
|
|
|
|
|
3.) Modifications to Makefiles, Perl, or JS code need a bugzilla bug with
|
2006-10-25 20:40:15 +00:00
|
|
|
davel and sayrer cc'd.
|
|
|
|
|
|
|
|
|
|
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?");
|
|
|
|
|
|
2006-10-26 18:57:34 +00:00
|
|
|
|
|
|
|
|
//
|
|
|
|
|
// 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?");
|
|
|
|
|
|
2006-10-25 20:40:15 +00:00
|
|
|
//
|
|
|
|
|
// 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>
|
