Testing Framework

From AbiWiki

Revision as of 20:21, 30 May 2009 (view source) Hub (Talk | contribs) ← Older edit		Current revision as of 13:19, 27 November 2010 (view source) Uwog (Talk | contribs) m (Reverted edits by Unotefuca (Talk) to last revision by Hub)
(2 intermediate revisions not shown)

---

Current revision as of 13:19, 27 November 2010

Contents 1 Unit Test 2 Regression Test 2.1 File import / export 2.2 Text backend

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:

1. file import export
2. 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.