Software Testing process Software testing process 1. Test Strategy and Test Plan Every project needs a Test Strategy and a Test Plan. These artifacts describe the scope for testing for a project: The systems that need to be tested, and any specific configurations Features and functions that are the focus of the project Non-functional requirements Test approach—traditional, exploratory, automation, etc.—or a mix Key processes to follow – for defects resolution, defects triage Tools—for logging defects, for test case scripting, for traceability Documentation to refer, and to produce as output Test environment requirements and setup Risks, dependencies, and contingencies Test Schedule Approval workflows Entry/Exit criteria And so on… Whatever methodology your project follows, you need to have a Test Strategy and Software Testing Plan in place. Make them two separate documents, or merge them into one. Without a clear test strategy and a detailed test plan, even Agile projects will find i...