Test plan maturation/evolvement
I am setting up a test documentation infrastructure using Excel for a web-based application. Each major area of functionality for the software will have its own Excel spreadsheet file. The first worksheet will cover regression tests for the area of functionality. The second worksheet will contain detailed test scenarios for new features. The third worksheet will contain specific tests for bug fixes (to ensure that the fix works and did not break anything else).
For each new release, each of these Excel files will have to be updated. The regression test worksheet will have the new feature test scenarios and the bug fix tests from the previous version integrated into it.
Maintaining this infrastructure will not be easy as the product grows in size, but any good base/repository for testing will have a large volume of tests.
Having provided this background, questions now arise about updating this structure. When integrating the new feature scenarios into the regression, do all of the scenarios get included? New feature testing tends to be more labour intensive and this will have many scenarios. Are all of these scenarios then transitioned to regression? Granted, one could filter out the scenarios that customers will never (or very rarely) use, but by not including it in the regression suite, does this not diminish the QA process? The premise for not including all scenarios into regression is due to the fact that regression testing will get bogged down with tests that may be too granular and thus unnecessarily prolong the testing cycle.
Any input on my questions, document structure, and test plan maturation/evolvement are welcome.
Thanks in advance,
Re: Test plan maturation/evolvement
You need to start adding a risk rating to ensure that your regression testing is focused. You can often maintain scripts by using tokens to reflect data (profiles, etc.) and by writing some simple VBA macros to merge scripts with data that are up to date. You can maintain many standard scripts in a workbook (multiple worksheets within a book to support multiple areas is a good idea). When you generate working scripts, however, you want to produce independent workbooks that can be used by different testers.