Testing Tools Survey: Difference between revisions

Testing Tools Survey (view source)

Revision as of 19:38, 2 February 2007

1,324 bytes added , 2 February 2007

no edit summary

Timr

2,088

edits

@@ Line 1: / Line 1: @@
+__TOC__
+= List of Modules =
 * Module: None
 ** Source Dirs: db, ipc, extensions/irc, extensions/metrics, extensions/schema-validation, extensions/universalchardet, extensions/webdav, extensions/webservices
@@ Line 513: / Line 515: @@
 ** Test Files: 15
 ** No response from e-mail.
+= Categories of Information =
+* Test suite/test procedure name
+** Any useful name that will uniquely identify the set of tests
+* Brief description of the test suite/procedure
+** Things like  the purpose and goals for the test suite/procudure.  What is the scope of the test suite/procudure.  Are there any major areas know to be missing from the test suite/procudure
+* Specific area tested?
+** What specific area of the product does the test suite/procudure cover.  Examples: DOM parser, Layout engine, key bindings.  If not targeted at a specific area, what is the main purpose of the test  suite/procudure.  Examples: performance, compatibility.
+* Test Harness
+** What framework or context does the test suite run in?
+** Examples: none, mochikit, XPCshell, jsunit, litmus, silk
+* Status of automation
+** Examples: manual procedure, computer guided, semi-automated (some maunal sets with setup, launching, verifying results), fully-automated
+* When is the test run?
+** Examples: every integration, nightly, every milestone, as needed/desired
+* How is the test run
+** Examples: in private test environment, by tinderboxes
+* Test Suite location
+** Examples: path in source tree, URL to test pages
+* Test Suite owner/maintainer
+** Who developed it, is championing it, and/or maintaining it