Automated Debugging (4): making problems fail - automated test for debugging

mainly talk about testing, from the point of view helping debugging

1. Overview

1) To test for debugging, one must...
* create a test to reproduce the problem
* run the test several times during debugging, and
* run the test before new releases to prevent regression

2) Automate as much as possible

3) To test at the presentation layer, simulate human interaction

4) To test at the functionality layer, use an automation interface

5) To test units, use the unit API to control it and assess its results

6) To isolate a unit, break dependencies using the dependency inversion principle

7) To design for debugging, reduce the amount of dependencies

8) A variety of techniques is available to prevent errors and problems

ZW comment 1: design for debugging is the interesting concept...Some more exploration

ZW comment 2: Memory past
1) dogtail for Frysk GUI test: Link to the author
2) JUnit test work in Amino team, parallel extension for JUnit
The amino project

http://amino-cbbs.blogspot.com/