 |
| |
Table of Contents
Testing is important. Matchbox is likely to be a key part of the system - even a minor bug can cause serious user problems. The asynchronous nature of X11, interdependencies of code mechanisms and the complexities of window management all can lead to the introduction of bugs when even minor code is added or modified. Therefore thorough testing is important to avoid such problems.
The best way to test Matchbox is 'in the wild' from real user usage and feedback, however this is not always practical - it's extremely useful to perform a standard set of tests after changes to the source code and before making a release. This document discusses: how to run Matchbox in a testing environment, how to use the test scripts included in the distribution and what to do if tests fail.
The documentation here is relevant for the 0.9 matchbox release.
| |