**Notes: What is Test Strategy in Software Testing - Software Testing Tutorial #39** **Understanding Test Strategy:** - Test Strategy is a vital testing document. - It differs from Test Plans but is often confused with it. - Understanding these documents is crucial for effective testing. **Key Sections in a Test Strategy Document:** 1. **Scope and Environment:** - Defines scope considerations for testing. - Addresses the test environment and its specifications. 2. **Testing Approach:** - Outlines how testing will be approached in the organization. - Defines testing levels like unit, integration, system, and user acceptance testing. 3. **Testing Tools:** - Specifies testing tools, including test management, defect management, and automation tools. - Standardizing tools across projects streamlines processes. 4. **Release Management:** - Describes how builds will be managed and when releases will occur during testing. - Includes information on build frequency and release processes. 5. **Risk Analysis:** - Considers risk analysis and outlines factors for projects to consider during testing.
6. **Reviews and Approvals:** - Defines reviewers and approvers for testing projects. - Reviewers and approvers play a crucial role in project validation and approval. **Test Strategy in Organization Hierarchy:** - In larger organizations, the Test Strategy is a high-level document applicable to the entire organization. - Individual projects have their own Test Plans. - Test Plans reference the high-level testing approach defined in the Test Strategy and adapt it to the project's specific needs. **Integration of Test Strategy and Test Plan:** - In small organizations with few projects, the Test Strategy may be included within the Test Plan. - In larger organizations, a separate Test Strategy document is beneficial to maintain consistency across multiple projects. **Conclusion:** - A Test Strategy is a high-level document defining the general approach to testing in an organization. - It ensures consistency in testing practices, tools, and processes across projects. - Test Plans are project-specific and elaborate on the testing approach defined in the Test Strategy.
It would be really helpful if you take a real time project as an example and then explain the Test Strategy and Test Plan documents based on this project by using real time examples of testing tools, test environment, scope, etc.
Good one. A test strategy is the process of pre-collecting all essential data points and connecting them well to pre-plan your software testing. It gives a clear idea about what to test, how to test, and when to test along with selecting the right testing tool. Automated testing platforms like Avo Assure helps software enterprises handle complex software testing in a seamless manner.
Tgank you very much for the great video. TS is verywell explained . I have been trying to get a clear picture of this for the past two days. Tried lots of websites & videos. No luck. At last, got it in this video. Thanks a ton. Please keep adding such detailed videos. Liking & subscribing
i dont understand ultimately, it seems he has strong knowledge but i'm not sync with his explanation. entire video is completed when i tries to understand his explanation. initial definition itself is not having clarity. i know that the persons who have knowledge may connect to his explanation.
**Notes: What is Test Strategy in Software Testing - Software Testing Tutorial #39**
**Understanding Test Strategy:**
- Test Strategy is a vital testing document.
- It differs from Test Plans but is often confused with it.
- Understanding these documents is crucial for effective testing.
**Key Sections in a Test Strategy Document:**
1. **Scope and Environment:**
- Defines scope considerations for testing.
- Addresses the test environment and its specifications.
2. **Testing Approach:**
- Outlines how testing will be approached in the organization.
- Defines testing levels like unit, integration, system, and user acceptance testing.
3. **Testing Tools:**
- Specifies testing tools, including test management, defect management, and automation tools.
- Standardizing tools across projects streamlines processes.
4. **Release Management:**
- Describes how builds will be managed and when releases will occur during testing.
- Includes information on build frequency and release processes.
5. **Risk Analysis:**
- Considers risk analysis and outlines factors for projects to consider during testing.
6. **Reviews and Approvals:**
- Defines reviewers and approvers for testing projects.
- Reviewers and approvers play a crucial role in project validation and approval.
**Test Strategy in Organization Hierarchy:**
- In larger organizations, the Test Strategy is a high-level document applicable to the entire organization.
- Individual projects have their own Test Plans.
- Test Plans reference the high-level testing approach defined in the Test Strategy and adapt it to the project's specific needs.
**Integration of Test Strategy and Test Plan:**
- In small organizations with few projects, the Test Strategy may be included within the Test Plan.
- In larger organizations, a separate Test Strategy document is beneficial to maintain consistency across multiple projects.
**Conclusion:**
- A Test Strategy is a high-level document defining the general approach to testing in an organization.
- It ensures consistency in testing practices, tools, and processes across projects.
- Test Plans are project-specific and elaborate on the testing approach defined in the Test Strategy.
Even though he's about 3 years late, my note man is still on duty. Thanks bro! xD
It would be really helpful if you take a real time project as an example and then explain the Test Strategy and Test Plan documents based on this project by using real time examples of testing tools, test environment, scope, etc.
Good one. A test strategy is the process of pre-collecting all essential data points and connecting them well to pre-plan your software testing. It gives a clear idea about what to test, how to test, and when to test along with selecting the right testing tool. Automated testing platforms like Avo Assure helps software enterprises handle complex software testing in a seamless manner.
Excellent video, thanks
Glad you liked it!
Tgank you very much for the great video. TS is verywell explained . I have been trying to get a clear picture of this for the past two days. Tried lots of websites & videos. No luck. At last, got it in this video. Thanks a ton. Please keep adding such detailed videos. Liking & subscribing
Glad it was helpful!
Keep watching for more videos and tutorials.
this was very helpful thank you so much!!
Glad it was helpful! Keep watching and sharing.
Very well articulated. Thank you, Mahesh!
Most welcome!
Keep watching for more videos.
Thank you sir
@softwaretestingmentor do you offer 1 on 1 istqb foundation level training in detail?
Thanks for this video sir 🙂
Most welcome
if you can write a problem strategy before joining a project?
Thanks
Thank you
is test plan project specific
Yes
Is there anyone who have written a test strategy for a Machine Learning Model Systems?
i dont understand ultimately, it seems he has strong knowledge but i'm not sync with his explanation. entire video is completed when i tries to understand his explanation. initial definition itself is not having clarity. i know that the persons who have knowledge may connect to his explanation.
Too lagging...for 5 minutes content made 15 minutes
just play at 2x speed
I don’t feel so. I feel it’s well explained. I have been trying to get a clear picture for the past two days. At last, got it in this video.
waste video not good explanation
sir come to our college @fanshawe we have shitty instructors for this subject
Thank you! I am glad my work is helpful! Regards, Manish