Software QA/Testing/Tester FAQs: How To Create a Test Strategy?




   Software QA/Testing

Glossary and Technical FAQs


PreviousGo to next page



Q: How do you create a test strategy? (Cont'd...)

Inputs for this process:
  • A description of the required hardware and software components, including test tools. This information comes from the test environment, including test tool data.
  • A description of roles and responsibilities of the resources required for the test and schedule constraints. This information comes from man-hours and schedules.
  • Testing methodology. This is based on known standards.
  • Functional and technical requirements of the application. This information comes from requirements, change request, technical and functional design documents.
  • Requirements that the system can not provide, e.g. system limitations.
Outputs for this process:
  • An approved and signed off test strategy document, test plan, including test cases.
  • Testing issues requiring resolution. Usually this requires additional negotiation at the project management level.
[Continued on next page...]


Q: Do you like this site?

A: Link to this page! From a forum, from a web site, or from a blog!



______________________________________________________

Copyright 2001-2011 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


     Go to next page