gecko/testing/mochitest
2013-04-09 17:13:32 -07:00
..
chrome Bug 855465 - Add emacs python mode comments to moz.build files; r=gps 2013-04-01 11:36:59 -07:00
dynamic Bug 855465 - Add emacs python mode comments to moz.build files; r=gps 2013-04-01 11:36:59 -07:00
MochiKit Bug 855465 - Add emacs python mode comments to moz.build files; r=gps 2013-04-01 11:36:59 -07:00
pywebsocket
roboextender Bug 855465 - Add emacs python mode comments to moz.build files; r=gps 2013-04-01 11:36:59 -07:00
ssltunnel Bug 855465 - Add emacs python mode comments to moz.build files; r=gps 2013-04-01 11:36:59 -07:00
static Bug 855465 - Add emacs python mode comments to moz.build files; r=gps 2013-04-01 11:36:59 -07:00
tests Bug 855465 - Add emacs python mode comments to moz.build files; r=gps 2013-04-01 11:36:59 -07:00
android.json Bug 838088 - Followup: Remove obsoleted entries from android.json. 2013-04-04 09:05:32 +02:00
b2g.json Backed out 2 changesets (bug 850362, bug 600307) for Windows XP leaks on a CLOSED TREE. 2013-04-11 17:00:28 -04:00
browser-harness.xul Bug 771271 - Get mochitest-metro-chrome tests running in immersive mode. r=jmaher 2013-02-12 14:51:24 -06:00
browser-test-overlay.xul
browser-test.js Bug 851516: browser-chrome should wait for delayedStartup. r=joe 2013-03-19 09:50:31 +01:00
cc-analyzer.js
chrome-harness.js
gen_template.pl
harness-overlay.xul
harness.xul
install.rdf
jar.mn Bug 404077: Add mochitest support (currently semi-disabled) for making tests fail when an unexpected number of assertions fire. r=ted 2013-02-24 23:42:38 -08:00
mach_commands.py Bug 857984 - mach mochitest now colorizes and prints failure summary; r=Ms2ger 2013-04-04 15:17:23 -07:00
Makefile.in Bug 854921 - Pass firefox path to metrotestharness so tests.ini can be written to a location that works with test zips / test slaves. Also add metro tests to mochitest tests.jar. r=mbrubeck, bbondy 2013-03-26 17:01:15 -05:00
manifest.webapp Bug 839519 - Add systemXHR permission. r=dclarke 2013-03-09 21:00:14 -05:00
moz.build Bug 855465 - Add emacs python mode comments to moz.build files; r=gps 2013-04-01 11:36:59 -07:00
plain-loop.html
pywebsocket_wrapper.py
README.txt
redirect.html
runtests.py Bug 835930 - move b2g unittest profile handling on top of mozbase instead of automation.py, r=jgriffin 2013-03-28 16:42:49 -04:00
runtestsb2g.py Bug 860108 - Clone starting repo for b2g desktop mochitests, r=ahal 2013-04-09 17:13:32 -07:00
runtestsremote.py Bug 833765 - Increase default sut timeout to 320 s during rc tests; r=jmaher DONTBUILD 2013-04-08 12:34:45 -06:00
runtestsvmware.py
server.js

 ----------------
 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>