Testing Framework
From AbiWiki
(Difference between revisions)
| (One intermediate revision not shown) | |||
| Line 1: | Line 1: | ||
| - | + | == Unit Test == | |
[[Unit Test]] of individual classes of AbiWord. This is the first step. If [[Unit Test]] does not pass, then there is problem. | [[Unit Test]] of individual classes of AbiWord. This is the first step. If [[Unit Test]] does not pass, then there is problem. | ||
The basic problem with AbiWord and unit testing is that most of the classes in both the [[Piece Table]] and the [[Formatter]] are too interdependent, therefor hard to unit tese. | The basic problem with AbiWord and unit testing is that most of the classes in both the [[Piece Table]] and the [[Formatter]] are too interdependent, therefor hard to unit tese. | ||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
| - | |||
== Regression Test == | == Regression Test == | ||
Current revision as of 13:19, 27 November 2010
Contents |
Unit Test
Unit Test of individual classes of AbiWord. This is the first step. If Unit Test does not pass, then there is problem.
The basic problem with AbiWord and unit testing is that most of the classes in both the Piece Table and the Formatter are too interdependent, therefor hard to unit tese.
Regression Test
Regression testing should be done for:
- file import export
- text backend.
Such a test suite should be run and pass before a release, either stable or development.
File import / export
The idea is to import defined set of documents and check the output.
When a new import feature is added, the test is modified to check that. It should help is track any possible side effects.
Text backend
Ideally, each backend bug should have a test written for it. That way you can validate the fix, and ensure it does not reappear.
