Difference between revisions of "Unit Testing"

From CDOT Wiki
Jump to: navigation, search
(→‎December 06, 2006)
(→‎Unit Testing Framework for Firefox)
Line 98: Line 98:
 
This framework will allow the participant to write unit test cases easily without knowing the UI, messages, and logs. They can focus on write test cases and the framework will take care the rest of the work.
 
This framework will allow the participant to write unit test cases easily without knowing the UI, messages, and logs. They can focus on write test cases and the framework will take care the rest of the work.
  
−
 
+
Click on '''[http://paulgu.com/download/mozilla/unittesting@paulgu.com.xpi Unit Testing framework]''' to download this unit testing framework.
  
 
=== Framework Structure ===
 
=== Framework Structure ===
Line 326: Line 326:
  
 
=== What I have learned ===
 
=== What I have learned ===
−
 
−
 
  
 
== Project News ==
 
== Project News ==

Revision as of 01:29, 8 December 2006

Project Name

JavaScript Unit Testing

Project Description

Use an existing unit testing framework (or create one) and demonstrate its use by writing a collection of unit tests that fully test a browser feature of your choosing. The framework will provide decent setup and teardown code that will enable the programmer to start the browser, run the tests, report pass/fail and shutdown the browser.

Project Leader(s)

Paul Yanchun Gu (IRC: gpaul)

Project Contributor(s)

Project Details

  • Had read the links from Dave, it's very interesting, it's called test_nodelist.

October 27, 2006

  • Had really hard time on trying to understand how to build and run a test case. This involves the following technologies that I had never learned before:
    • XUL
    • install.rdf
    • chrome.manifest
    • Extension Wizard generator

November 9, 2006

  • When I try to run the bookmark tester, I got this error:
    • Error: uncaught exception: [Exception... "Could not convert JavaScript argument" nsresult: "0x80570009 (NS_ERROR_XPC_BAD_CONVERT_JS)" location: "JS frame :: chrome://bookmarkstester/content/testerWindow.js :: <TOP_LEVEL> :: line 134" data: no]

November 10, 2006

  • Fixed exception error, change window.attachEvent("onload", testerWindow.startup(), false) to window.attachEvent("onload", testerWindow.startup, false);
  • Trying to get error console working for debugging ...
  • dump, setting the preference browser.dom.window.dump.enabled to true in Firefox, then start FF in console: -console
  • DOM:window

November 12, 2006

  • Try to find most function calls in Firefox, cannot get it work.
  • Try to display the firefox console for debugging ,the Firefox 2 cannot brings up console when I tried to user command: firefox.exe -console. In error console from the firefox menu, it displayed an error message: cannot recongnize the command -console.

November 18, 2006

November 19, 2006

First unit testing attempt.gif


This is screen shot before search
Bookmarks manager before.jpg

This is screen shot after search
Bookmarks manager after.jpg


  • Spent a whole day on trying to debug firefox API... no documentation... man ===

November 20, 2006

December 06, 2006

  • Code documentation.
  • Instruction on how to write test cases by using this framework

December 07, 2006

  • Finished documentation of the framework


Unit Testing Framework for Firefox

Introduction of this framework

Unit Testing is an approach of programmatic testing of software. The participant will take a section of code and write unit tests for it, so they can find any possible bugs that may exist in the code.

This framework will allow the participant to write unit test cases easily without knowing the UI, messages, and logs. They can focus on write test cases and the framework will take care the rest of the work.

Click on Unit Testing framework to download this unit testing framework.

Framework Structure

This framework is an extension of Firefox, it has the common structure that the extension has. This is also a special extension that allows the participant to extend it to many types of unit testing. In following sections, I will use the screen shots to explain the details of the framework.

Structure01.png
From the above screen shot, we can see this framework name is unittesting@paulgu.com, and it contains the following folder and files:

  • content. It contains the framework code and unit testing code.
  • default. This holds default preferences of this extension.
  • local. This contains the language settings of this extension.
  • skin. This is the style of the extension.
  • build.sh, chrome.manifest, config_build.sh, install.rdf, and readme.txt are standard files of the extension. They contains installation information.


Structure02.png
This screen shot is showing us a detail list of the famework file in the content folder.

  • It contains the jsUnitTest core files which start with jsUnitTest.
  • It also contains Unit Testing framework files which start with unittesting.


The files starting with is the core framework files.

  • unittesting.js, holds the unit test cases that need to be tested.
  • unittestingDisplay.js, is responsible for displaying message to UI.
  • unittestingLog.js, is responsible for logging message to the error console or log file.
  • unittestingOverlay.js, is responsible for populating the GUI window.
  • unittestingWindow.js, holds all the unit testing functions
  • unittestingWindow.xul, is responsible for loading the framework and updating UI elements.


How to add test cases by using this framework

Writing the test cases by using this framework is really easy. All you need to to is opening the file unittesting.js, and add any type of test case by adding following three sections. (This example is for bookmarks unit testing)

  • Section 1. Initialize the services (Firefox API) that contains all the units that are going to be tested. The following is the example of bookmarks services in Firefox API. 
/* 
 * test units initialization
 *
 * In this part, you need to initialize the services that contains all the units
 *
 * EXAMPLE: initialize Bookmark Service
 * this._RDF        = Components.classes["@mozilla.org/rdf/rdf-service;1"].getService(Components.interfaces.nsIRDFService);
 * this._kBMSVCIID  = Components.interfaces.nsIBookmarksService;
 * this._BMDS       = this._RDF.GetDataSource("rdf:bookmarks");
 * this._BMSVC      = this._BMDS.QueryInterface(this._kBMSVCIID);
 *
---------------------------------------------------------------------------*/
function BookmarksTests() {
    logText("initializing bookmarksTests");
    this.browserWindow = window.opener;

    this._RDF       = Components.classes["@mozilla.org/rdf/rdf-service;1"].getService(Components.interfaces.nsIRDFService);
    this._kBMSVCIID = Components.interfaces.nsIBookmarksService;
    this._BMDS      = this._RDF.GetDataSource("rdf:bookmarks");
    this._BMSVC     = this._BMDS.QueryInterface(this._kBMSVCIID);

    this.totalTests = countTests(suite);
    logText("finished initializing bookmarksTests");
}

/* 
 * bookmark test window initialization
 * 
 * setUp is for initializing services in the firefox API
 * 
---------------------------------------------------------------------------*/
var bookmarkstestWindow = {
    pass: true,

    setUp: function() {
        logText("Unit Testing Window startup");
        this.bookmarksTests = new BookmarksTests(); // initialize bookmark unit tests 
        this.testsRun = new Array();
        logText("finished unit testing startup");
    },

    tearDown: function() {
    }
};

/* 
 * initialize bookmarks test window
 * 
---------------------------------------------------------------------------*/
window.addEventListener("load", bookmarkstestWindow.setUp, false);


  • Section 2. A test suite holding all the test cases.The following is example of bookmarks test suite.
/* 
 * test suite
 * 
 * This is the test suite that contains all the test cases
 * Here is the sample of the bookmarks testing, the following unit will be 
 * tested: 
 *      testCreateBookmark
 *      testRemoveBookmark
 *      testCreateFolder
 *      testDeleteFolder
 *      testBookmarkAllTabs
 * 
---------------------------------------------------------------------------*/
var suite = {
    testManager: function() {
        try {
            assertNotUndefined(bookmarksTests._BMSVC);
            unittestingWindow.passTest("Test Manager");
        } catch (e) {
            Components.utils.reportError("Exception from testManager() : " + e);
        }
    },

    /*
     *  Unit testing function: testCreateBookmark().
     */
    testCreateBookmark: function() {
        try {         
  
            var res = bookmarksTests._BMSVC.createBookmark("paulgu.com", 
                "http://www.paulgu.com/", "iso-8859-1", "Paul Yanchun Gu", "", null);
            
            // isBookmarkedResource() is not working, 
            // I don't know what type of rSource should be
            var rSource = "http://www.paulgu.com/";

            //check if the bookmark is created successfully
            var result = assert(bookmarksTests._BMSVC.isBookmarkedResource(rSource));

            if(result == true) {
                // if success, testing passed
                unittestingWindow.passTest("Create Bookmark ");
            } else {
                // too bad, testing failded
                unittestingWindow.failTest("Create Bookmark ");
            }
        } catch (e) {
                // Exception
            Components.utils.reportError("Exception from testCreateBookmark() : " + e);
        }
    },

    /*
     *  Unit testing function: testRemoveBookmark().
     */
    testRemoveBookmark: function() {
        // need to be developed
    },

    /*
     *  Unit testing function: testCreateFolder().
     */
    testCreateFolder: function() {
        // need to be developed
    },

    /*
     *  Unit testing function: testDeleteFolder().
     */
    testDeleteFolder: function() {
        // need to be developed
    },

    /*
     *  Unit testing function: testBookmarkAllTabs().
     */
    testBookmarkAllTabs: function() {
        // need to be developed
    }
};


  • Section 3. Run your test cases. In this example, we run bookmarksTests.
/* 
 * run the tests
 * 
 * This is the main function that trigger the tests
 * 
---------------------------------------------------------------------------*/
function runTests() {
    runUnitTests(bookmarksTests);
}


Customize Extension Item Name

If users want to change the menu item name, they can open file unittesting.dtd under folder local.

Extension02.png

And then they can change the first item in the file unittesting.dtd.

Extension03.png


Run the tests

After adding the test cases to the extension, the participant can install the extension by drag and drop the extension into Firefox, and they could see the following screen in Firefox.

Extension01.png

Select the Unit Testing, system will pop up the test window as following.

Extension04.png

Users can also open the error console window to watch all testing logs. Here is the console window.

Extension05.png

Now click on the run button on test window. All logs will be displayed in console.

Extension06.png

Unfortunately, the test windows cannot be displayed, because it hasn't been developed.

Extension07.png

What have done

What need to be continued

What I have learned

Project News

  • Wednesday, September 20, 2006 1:07 pm, Rob helped me to get start on JSUnit Testing.
  • Monday, September 18, 2006 8:36 am, Dave helped me to connect to Rob Campbell, who is from Mozilla QA team. He explained to me about Unit Testing used in Mozilla.
  • Wednesday, October 4, 2006, Saw this interesting post about test cases in Mozilla, and the code example is quite useful.
Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=Unit_Testing&oldid=7546"