How to Upgrade Test Plan

Test plans should be upgraded each time the application is updated.

Software engineers and computer programmers team up to create or update software applications used for both business and personal use. This involves designing the software application, deciding what functions it will ultimately perform, writing the code and then testing it to make sure it performs properly. Test plans are drawn up before the software is built as part of the quality process. Whenever the software needs updates, the test plans also need corresponding updates.

Things You'll Need

• Current test plans
• Software program, word processing or developer environment (optional)

Instructions

1. Write down exactly what the new software specifications are suppose to do. For example, "When user presses 'Compare' button, the results will appear in the text box."

2. Determine a deadline for the new test plan to be complete and approved. Write down the deadline.

3. Review the current software testing plans. Determine the exact location in the current testing process where the new tests should occur. For example, if the original testing plan calls for an accuracy test verifying the initial data that was input is correct, then a logical place for the new test would be to compare the results for accuracy just after the results are displayed in the text box.

4. Write out possible results that could be on display that are both correct and incorrect to test the new upgrade. For example, "28 or 25 = 28 is bigger: correct," " 32 or 15 = 32 is bigger: correct," and "15 or 27 = 15 is bigger: not correct," would be some suitable scenarios.

5. Continue reviewing the current test plans and inserting new testing modules where applicable. Input this same information into the chosen software program the current test plans are held in and save your work when you finish.

Tips & Warnings

• Consider forming an independent group of testers to try and "break" the software application during the testing processes. This will allow both the computer programmers and the software engineers to feel less bias about the work that has gone into the application when it comes time to test the application for its true limitations.

• Don't expect testing to find every single error that may be present in the software application. Your testing plans should include incremental benchmarks for testing on the smallest unit levels throughout the development process to decrease the amount of errors that end users may find later.

References

• "Software Engineering A Practitioner's Approach, Sixth Edition"; Roger S. Pressman; 2005