SoftwareTesting:Tools:UnitTest: Difference between revisions
Jump to navigation
Jump to search
(→Tasks) |
(→Tasks) |
||
| Line 9: | Line 9: | ||
# <strike>Create base MinUnit headers in mozilla/testing</strike> | # <strike>Create base MinUnit headers in mozilla/testing</strike> | ||
# Implement example MinUnit Unit Tests | # Implement example MinUnit Unit Tests | ||
# Create [http://www.gamesfromwithin.com/articles/0512/000103.html CppUnitLite] in mozilla/testing | # <strike>Create [http://www.gamesfromwithin.com/articles/0512/000103.html CppUnitLite] in mozilla/testing</strike> | ||
# Implement example CppUnitLite Unit Tests | # Implement example CppUnitLite Unit Tests | ||
# Create [http://cxxtest.sourceforge.net/ CxxTest] in mozilla/testing | # <strike>Create [http://cxxtest.sourceforge.net/ CxxTest] in mozilla/testing</strike> | ||
# Implement example CxxTest Unit Tests | # Implement example CxxTest Unit Tests | ||
# Reporting mechanism / framework | # Reporting mechanism / framework | ||
Revision as of 19:41, 10 July 2006
(see 343673)
Description
What is a “unit”? It can be a module, a class, a method or even a single block of code. Any encapsulation can be considered a unit and is up to the developer to define. A suite of tests can be written to test correctness of the unit and assert that a piece of code evaluates to true.
Tasks
Create base MinUnit headers in mozilla/testing- Implement example MinUnit Unit Tests
Create CppUnitLite in mozilla/testing- Implement example CppUnitLite Unit Tests
Create CxxTest in mozilla/testing- Implement example CxxTest Unit Tests
- Reporting mechanism / framework
- Tinderbox?
Issues
- cvs access
- discussions to find and create more tests
- reporting mechanism still TBD
- testing platform still TBD