1
edit
Changes
→How to Get Involved
Basic Advice:
* You '''must''' be able to automate the test--no human intervention is allowed.
* Possible test types include: crashing*: '''Crashing'''*:: Can you crash the program with a minimal collection of circumstances (steps) that are easily reproducable? (In other words, performancecan you write a script so that this happens in a controlled manner.)*: '''Performance-related, '''*:: Is there a threshold for unacceptable consumption of time and/or space that is reason for concern?*: '''Program hanging'''*:: Does the program hang? Will it occur in a certain functionality of the software that is possible to isolate (reproduce) through scripted means?*: '''Unexpected return codes'''*:: What is a normal return code for the program hanging, ? What is considered unexpected ? Script a series of actions and pass the return codescode up to the test framework.
* Each test will fit into the test framework (which, at this point, still has to be designed). The tests must follow a few rules (again, undecided at this point).
Please check back in a few days. Expect some templates and samples up shortly to help get you going. <u>The currently listed test types are subject to change.</u>
