SoftwareTesting:Tools:UnitTest: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 3: | Line 3: | ||
== Description == | == Description == | ||
What is a | 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 test asserts that a piece of code evaluates to true. A suite of tests can be written to test correctness of the unit. | ||
== Tasks == | == Tasks == | ||
| Line 22: | Line 22: | ||
# reporting mechanism still TBD | # reporting mechanism still TBD | ||
# testing platform still TBD | # testing platform still TBD | ||
[[Category:SoftwareTesting]] | |||
Latest revision as of 21:29, 16 September 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 test asserts that a piece of code evaluates to true. A suite of tests can be written to test correctness of the unit.
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