QA/TDAI/Inventory
Jump to navigation
Jump to search
We all want quality to happen. How can we help? What is being run? What can I run something with? What does any of this mean? Not all questions are answered, but some.
This document has three sections:
- Test Harnesses - tools, designed to run tests. A harness may be targeted to a specific set of tests, or general to many kinds of tests. What test do you want to see run? Different harnesses could be used to run a given test. Which harness is better for which kinds of testing? kinds of testing?
- Test Suites - arbitrary groupings of test cases, roughly organized by functional area
- Test Infrastructure - the environments the test tools and test cases run in. This includes machine, operating system and physical location (ex: QA farm vs QA lab vs someone's desktop)
Test Harnesses
Test Harness Name | Brief Description | Language Used | Status of Harness | Notes |
MochiTest | based on the MochiKit framework | JavaScript | Invocation by buildbot on QA machines is being set up. Invocation of tests by inidividuals on built trunk is possible with setup. Currently being made to work in automated test harnesses. | [MochiTest on devmo] |
jsunit | JavaScript | |||
Acid2 | Web Standards Project compliance test page(s) | [Stds page] | ||
litmus | Catalog of manual test cases | English, German, French, etc. | The place to be on Community Test Day! | [main site] |
xpcshell | lots of under-the-hood XPCOM smarts! | some JavaScript, much C++ | [xpcshell on devmo] | |
SpiderMonkey | used only for the js/tests by bc, et al, for JS testing | JavaScript | [bc's page] | |
reftest | comparison of two pages, via JavaScript and Canvas, for visual equivalency | JavaScript | runnable on built trunk | [reftest on devmo] |
jssh | a javascript shell. What more can you say? | JavaScript | described as "largely defunct" | |
Tp | test of page loading | currently runs in tinderbox | ||
Tp2 | test of page loading | being developed to run in buildbot | ||
T* | includes Tdhtml, Ts, Txul, Trender (aka Tgfx), Z, and mZ | [most T] [Trender] | ||
'Browser and Eyeballs' | The most common test harness in use today. | wetware | There is a new tester born every day! :-) | |
Download Checker | listed as "run manually by QA" ??? | [wiki page] | ||
Software Update Checker | listed as "run manually by QA" ??? | [wiki page] | ||
l10n Search Verifier | listed as "run manually by QA" ??? | [wiki page] |
Test Suites
Test Suite Name | Brief Description | Test Harness(es) | Status | Notes | Owner |
JS tests | well-developed suite of tests of the JavaScript language | Custom framework in js/tests. Runs on QA Farm. | Semi-automated. Plans to fully automate with Alice and Rob's help in Q1 2007 | Run in customized harness, stable and not necessary to use or share. | bc |
Security tests | Custom framework. Runs on QA Farm. | Semi-automated. Plans to fully automate with Eggplant in Q1 2007 | When bugs were filed, regression test cases are usually added. | bc@mozilla.com | |
Automated Smoke Tests - FFx 1.5 | Eggplant. Runs on Tracy's machines. | Fully automated. Completed porting to Mac and Linux in Q4 2006. Plan to move executiion to QA Farm in Q1 2007 | A "Smoke Test" is a quick, basic qualification. | tracy@mozilla.com | |
Automated Smoke Tests - FFx 2.0 | Eggplant, runs on Tracy's machines. Originally a litmus suite. | Fully automated. Completed porting 1.5 tests to the 3 platforms for 2.0 in Q4 2006. Plan to move execution to QA Farm in Q1 2007 | tracy@mozilla.com | ||
Basic Functionality Tests (BFT) | 130+ manual test cases, broadly covering major features | for 1.5 and 2.0 | |||
Full Functionality Tests (FFT) | approx. 280 manual test cases, covering most features | for 1.0, 1.5 and 2.0 | |||
Localization Tests | 15 test cases | for 1.5 and 2.0 | |||
Software Update Suite | approx. 50 tests, targeted to update process itself | litmus | |||
Browser/Content | Will be transitioned to reftest or MochiTest, as appropriate. | custom executable/C++ |
browser/components/places=9 |
||
Buster | re-purposing of the Adobe Xalan tests. | custom executable/C++ | Driver is in mozilla, but test content gets re-downloaded. | content/xslt/buster I have received info from Jonas on the location of this. |
|
DOM | browser and eyeballs? | ||||
Embedding | custom executable/C++ | ||||
Extensions | custom executable/C++ | extensions/canvas3d=6 extensions/java/xpcom=10 extensions/metrics=5 extensions/mono=5 extensions/python=31 extensions/schema-validation=9 extensions/spatialnavigation=5 extensions/universalchardet=2 extensions/webdav=1 |
|||
Graphics | custom executable/C++ | gfx=8 | |||
HTML Parsing | custom executable/C++ (non-functioning). Moving to WHATWG/html5lib tests [366936] | [README] parser/htmlparser=327 |
Blake Kaplan | ||
I18N | custom executable/C++ | intl=37 | |||
XPConnect | custom executable/C++ | js/src/xpconnect=142 | |||
Layout/HTML | "the old regression test suite" and reftest. Older tests will go to reftest. | There are a lot of test files here. It is hard to say how current or correct they are. | |||
Math/ML | Do mathematical glyphs display correctly on all platforms? | "browsers and eyeballs" | also using w3c.org site content | layout/mathml=7 | |
??? | modules/libjar=4 modules/oji=758 modules/plugin=63 |
||||
Networking | custom executable/C++ | netwerk=121 | |||
NSPR | custom executable/c | nsprpub/lib=3 | |||
RDF | custom executable/C++ | rdf=11 | |||
Security/NSS | custom executable/C++ and "make check" | security/dbm=0 security/nss=56 |
|||
XPCOM | custom executable/C++ | xpcom/proxy=6 xpcom=66 |
|||
XPFE | JavaScript/XULRunner? | xpfe=3 | |||
XPInstall | ??? | xpinstall=3 |
Test Infrastructures
Test Infrastructure Name | Brief Description | Harnesses and Test Suites in the Infrastructure | Status of the Instructure | Notes |
tinderboxen | Continuous build engine for Mozilla source, much chronicled in song and fable. | "make check", the results of which may not be verified | see dynamic Tinderbox display | |
buildbots | Continuous build engines, written in Python, cycling rapidly based on Bonsai checkins. | "make check", reftest and MochiTest | reported via MozillaTest tinderbox | |
QA Farm | some number of Windows, Linux and Macs. Details are not important. They should be a black box resource for developers to say "test this". | "make check", reftest and MochiTest |