mckoss / pageforest

Automatically exported from code.google.com/p/pageforest
0 stars 0 forks source link

Unit Testing Example #22

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Since we have many of our JavaScript unit tests running in the browser, we can 
have a Hudson-like application that executes and displays test results 
directly in Pageforest.

Description

The unittest application prompts enter data for unit testing.  For each 
TestSuite to be run the user enters:

- Title
- namespace of TestSuite
- namespace(s) of any supporting dependencies (optional - the loader can 
demand load dependencies).

For each namespace, the user must enter:

- namespace name (e.g., org.starpad.format)
- location of file to load namespace (url)

When a test is run we collect:

- date/time of run
- browser version (user agent)
- duration of test run
- # tests run
- # tests fail

The application has a test manager, listing all the tests, and a graph of 
their historical results (# of tests, and # errors).
Demonstrates

Securely running javascript from within an application (Iframing documents).  
We may need to explicitly allow Pageforest scripting from particular test 
urls, so we can use this to do inteegration testing against Pageforest apps 
themselves.

Collecting data from diverse users (into document blobs), and using the LIST 
command to pull summary data into a report.

Audience

This application will directly appeal to Javascipt developers, giving them a 
tool similar to Hudson, to run, manage, and report on the progress of their 
testing framework.

Original issue reported on code.google.com by mckoss@gmail.com on 29 May 2010 at 3:23

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago

Original comment by jcrocholl on 1 Jun 2010 at 7:03