Software QA/Testing
Glossary and Technical FAQs
Q: How do you create a test plan/design? (Cont'd...) Inputs for this process:
- Test data is captured and base lined, prior to testing. This data serves as the foundation for unit and system testing and used to exercise system functionality in a controlled environment.
- Some output data is also base-lined for future comparison. Base-lined data is used to support future application maintenance via regression testing.
- A pretest meeting is held to assess the readiness of the application and the environment and data to be tested. A test readiness document is created to indicate the status of the entrance criteria of the release.
Outputs for this process:
- Approved Test Strategy Document.
- Test tools, or automated test tools, if applicable.
- Previously developed scripts, if applicable.
- Test documentation problems uncovered as a result of testing.
- A good understanding of software complexity and module path coverage, derived from general and detailed design documents, e.g. software design document, source code, and software complexity data.
[Continued on next page...]
- Approved documents of test scenarios, test cases, test conditions, and test data.
- Reports of software design issues, given to software developers for correction.
______________________________________________________
Copyright 2000-2010 by Rob Davis PE. All rights are reserved. No part of
this document may be reproduced in any form whatsoever
without written permission from Rob Davis, PE.
http://www.softwaretestengineer.com
http://www.robdavispe.com
