1. Introduction Current state of testing –Ad hoc, informal acceptance testing Why a more systematic process is needed –Increase thoroughness and sophistication – Automate –Provide a record of quality control –Prioritize further work Specific recommendations

2. Unit Testing Proposed for post-processing –To ensure compatibility with supported application versions –Implementation JUnit Write a driver and if needed stubs

3. Bug Reports and Tracking Bread and butter of software testing Bug report form –http://www.osc.edu/~srb/columbus/templat e.xmlhttp://www.osc.edu/~srb/columbus/templat e.xml Bug tracking tool –PCS ? –BugzillaBugzilla Backups

4. GUI Testing Ensure that inputted data is used and and used correctly Automation –High initial cost –3 to 10 times to break even –Capture and Replay Expect Human Factors –Style Consistency –Intuitive Layout and Defaults

5. Testing Plan Versioning and CVS Tagging Bug Report and Tracking Documentation - Software Combo Testing Thorough Client Testing Automate a Couple of Tests Misc. –JLintJLint –Plaform specific testing