View source for Mobile/Fennec Unittests/NewTests

== Overview ==

To create unittests on fennec, we will be focusing on [[https://developer.mozilla.org/en/Browser_chrome_tests Browser-Chrome]] type of tests.  As time goes on we might make a focus for reftest, crashtest, plain mochitest, chrome mochitest, a11y mochitests, or even xpcshell.  I am leaving Talos off the plate for now, but that is the other type of tests we have created to date.

== A Sample Browser-Chrome Test ==

[[http://mxr.mozilla.org/mobile-browser/source/chrome/tests/browser_bookmarks.js bookmarks]]

<pre>
gTests.push({
  desc: "Test adding a bookmark with the Star button",
  _currenttab: null,

  run: function() {
    this._currenttab = Browser.addTab(testURL_01, true);

    // Need to wait until the page is loaded
    this._currenttab.browser.addEventListener("load", 
    function() {
      gCurrentTest._currenttab.browser.removeEventListener("load", arguments.callee, true);
      gCurrentTest.onPageReady();
    }, 
    true);
  },
  
  onPageReady: function() {
    var starbutton = document.getElementById("tool-star");
    starbutton.click();    
    
    var bookmarkItem = PlacesUtils.getMostRecentBookmarkForURI(makeURI(testURL_01));
    ok(bookmarkItem != -1, testURL_01 + " should be added.");

    Browser.closeTab(gCurrentTest._currenttab);
    
    runNextTest();
  }  
});
</pre>

== Creating and Debugging ==

Creating a browser-chrome test is pretty much pure javascript that runs inside of chrome (for access to xul elements and full privilege content) extension.  We run this via the mochitest harness.

Currently we have a set of [[http://mxr.mozilla.org/mobile-browser/source/chrome/tests/ tests developed]], and all future tests should go in the same location.

To create a test, either add a new test case into an existing file or start with a new file.  Please use existing tests cases as an example of how to add tests and access components.

While creating tests, I highly recommend installing [[http://people.mozilla.org/~jmaher/dom_inspector-2.0.3.xpi DOM inspector]] (NOTE: this is a hacked up 2.0.3 version to install in fennec).  This doesn't work well on mobile devices, but running on a desktop build will be very powerful.  In order to use this in Fennec, you need to install it, restart, then type CTRL+SHIFT+I (similar to [[http://elvis314.wordpress.com/2009/05/20/using-dom-inspector-with-fennec/ these instructions]].)

== List of Tests We Need ==

[[https://bugzilla.mozilla.org/show_bug.cgi?id=553474 Tracking Bug]] for different areas that need test cases


bugs that have been fixed that we should add test cases for:
* https://bugzilla.mozilla.org/show_bug.cgi?id=490285
* https://bugzilla.mozilla.org/show_bug.cgi?id=510917
* https://bugzilla.mozilla.org/show_bug.cgi?id=466770
* https://bugzilla.mozilla.org/show_bug.cgi?id=456077
* https://bugzilla.mozilla.org/show_bug.cgi?id=434573
* https://bugzilla.mozilla.org/show_bug.cgi?id=454613
* https://bugzilla.mozilla.org/show_bug.cgi?id=436083 (need more tests?)
* https://bugzilla.mozilla.org/show_bug.cgi?id=518470
* https://bugzilla.mozilla.org/show_bug.cgi?id=523718
* https://bugzilla.mozilla.org/show_bug.cgi?id=524543 (zoom tests)
* https://bugzilla.mozilla.org/show_bug.cgi?id=551516
* https://bugzilla.mozilla.org/show_bug.cgi?id=556016 (possible click radius)
* https://bugzilla.mozilla.org/show_bug.cgi?id=561733 (need more tests?)