Difference between revisions of "Unit Testing"

From CDOT Wiki
Jump to: navigation, search
(Project Name)
(Project Description)
Line 5: Line 5:
 
== Project Description ==
 
== Project Description ==
  
Description should be no longer than a paragraphInclude links to any relevant on-line resources. For example, http://google.com or [http://developer.mozilla.org MDC].
+
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) ==
 
== Project Leader(s) ==

Revision as of 22:47, 20 September 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)

Name(s) of primary people working on the project. If you want to join a project as leader, discuss with other leaders first. Include links to personal pages within wiki

Project Contributor(s)

Name(s) of people casually working on the project, or who have contributed significant help. Include links to personal pages within wiki

NOTE: only Project Leader(s) should add names here. You can’t add your own name to the Contributor list.

Project Details

Provides more depth than the Project Description. This is the place for technical discussions, project specs, or other details. If this gets very long, you might consider breaking this part into multiple pages and linking to them.

Project News

This is where your regular updates will go. In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc.

Put detailed technical information into the Project Details page (i.e., update it as you go), and save this section for news about participation in the project.