**Notes: Test Plan vs. Test Strategy - Software Testing Tutorial #40** **Test Strategy:** - **Organizational Level:** Defined at the organizational level. - **High-Level Vision:** Provides a high-level vision for testing approaches and processes. - **Answers "Why" Questions:** Answers the "why" questions regarding testing approaches. - **Consistency Across Organization:** Designed to maintain consistency in testing practices across the organization. - **Stability:** Remains relatively stable and does not change frequently. **Test Plan:** - **Project Level:** Defined at the project level. - **Specific Approach:** Outlines the specific approach to testing for a particular project. - **Answers "How" Questions:** Answers the "how" questions related to testing execution. - **Project-Specific:** More detailed and includes project-specific information. - **Flexibility:** Can change frequently as more project details become available. **Relationship Between Test Strategy and Test Plan:** - **Reference Point:** Test plans refer to the overarching test strategy document. - **Common Understanding:** The test strategy provides a common understanding of testing practices, tools, and processes across the organization. - **Tailoring for Projects:** Projects use the test strategy as a reference point to create detailed test plans tailored to their specific needs. - **Elaboration:** Test plans elaborate on the strategy, including project-specific details such as test coverage, scheduling, resource allocation, and timelines. **Integration of Test Strategy and Test Plan:** - **Small Organizations:** In small organizations with one or two projects, a separate test strategy document may not be necessary. - **Combined Document:** In such cases, the test plan can include both project-specific details and high-level strategy. - **Large Organizations:** In larger organizations, maintaining a distinct test strategy document is beneficial to ensure consistency across various projects. **Conclusion:** - **Test Strategy:** The "why" document outlining the overarching testing approach for an organization. - **Test Plan:** The "how" document specifying the detailed testing approach for a particular project. - **Relationship:** Test plans draw from the test strategy, ensuring common practices and tools while adapting to project-specific requirements.
How can someone dislike it . I wonder . How nicely explained . The example initially you gave really helped in going through the points separately. The way you explain is really good . No doubts left .. thank you 😊
Hi Very nice videos I have a query, In agile process where user stories are there...is there need to create test plan. If yes then what should incorporate in test plan.
Could you please let me know which one should be written first - test plan or test strategy? I was asked this in an interview. I told "test plan is written first" which I think is wrong. Thank you.
Sir Congrats! You have explained some very confusing terms in easy to understand manner. Thanks a ton! Would you be creating a playlist on ISTQB Advanced certifications in the near future?
You have taken IBM. The IBM will be having many verticals which means they have a different strategies for every vertical. Then, the test plan is organised with the help of Test Architect for the Project. Lost! What are the various or set of Test Strategies IBM is having. Which are the Test Strategies used for BIMM tools like QIMM.
Man! The whole time you are covering 20% of the board trying to jump into the frame. I can't see shit written on the left side. But that said, the explanation was great.
![[4K] Watch SpaceX Catch A Starship Rocket From Space!!! #IFT5](http://i.ytimg.com/vi/pIKI7y3DTXk/mqdefault.jpg)
**Notes: Test Plan vs. Test Strategy - Software Testing Tutorial #40**
**Test Strategy:**
- **Organizational Level:** Defined at the organizational level.
- **High-Level Vision:** Provides a high-level vision for testing approaches and processes.
- **Answers "Why" Questions:** Answers the "why" questions regarding testing approaches.
- **Consistency Across Organization:** Designed to maintain consistency in testing practices across the organization.
- **Stability:** Remains relatively stable and does not change frequently.
**Test Plan:**
- **Project Level:** Defined at the project level.
- **Specific Approach:** Outlines the specific approach to testing for a particular project.
- **Answers "How" Questions:** Answers the "how" questions related to testing execution.
- **Project-Specific:** More detailed and includes project-specific information.
- **Flexibility:** Can change frequently as more project details become available.
**Relationship Between Test Strategy and Test Plan:**
- **Reference Point:** Test plans refer to the overarching test strategy document.
- **Common Understanding:** The test strategy provides a common understanding of testing practices, tools, and processes across the organization.
- **Tailoring for Projects:** Projects use the test strategy as a reference point to create detailed test plans tailored to their specific needs.
- **Elaboration:** Test plans elaborate on the strategy, including project-specific details such as test coverage, scheduling, resource allocation, and timelines.
**Integration of Test Strategy and Test Plan:**
- **Small Organizations:** In small organizations with one or two projects, a separate test strategy document may not be necessary.
- **Combined Document:** In such cases, the test plan can include both project-specific details and high-level strategy.
- **Large Organizations:** In larger organizations, maintaining a distinct test strategy document is beneficial to ensure consistency across various projects.
**Conclusion:**
- **Test Strategy:** The "why" document outlining the overarching testing approach for an organization.
- **Test Plan:** The "how" document specifying the detailed testing approach for a particular project.
- **Relationship:** Test plans draw from the test strategy, ensuring common practices and tools while adapting to project-specific requirements.
Bro Great explaination kudos, an interviewer asked me this as I was confused I confused him as well at the end he wasn't sure too.😂
😂
😂😂😂
😆😆
🤣🤣🤣 if you cant convince them, confuse them, you understood the assignment
Out of all the Indian Instructors I have watched, yours is the easiest to watch and understand. Subscribed!
i agree!!!!
I watched many videos related to this topic and now after watching your video I finally understood V model. Tysm Sir!!
I click " like" before even starting to view. Have been following your videos, you doing great job. Thanks.
How can someone dislike it . I wonder . How nicely explained . The example initially you gave really helped in going through the points separately. The way you explain is really good . No doubts left .. thank you 😊
Thank you Nibha! I am glad my work is helpful! Keep learning and sharing!
Explaining through examples make it more clear, and that is what I have always seen in your videos. Thank you.
Very nice and clear explanation 😊
Hi
Very nice videos
I have a query, In agile process where user stories are there...is there need to create test plan.
If yes then what should incorporate in test plan.
Awesome explanation. So clear. Thanks for your effort and time to record this video!
You're very welcome!
Keep watching and subscribe for more videos and tutorials.
Very Helpful.Thanks
Is it common to create a test plan or test strategy in agile?
Thank you so much, it's much clearer now
Glad to hear that! Keep watching and sharing.
Amazing so well explained clean crisp and clear to the point
very useful and super clear. Great work.
Glad it was helpful!
Thanks you for clear explanation
Glad it was helpful! Thank you very much. keep watching and sharing!
Thanks for the informative video, Sir
Thank you very much. Keep watching and sharing.
Excellent knowledge, thank you
You are welcome😊
Keep watching for more videos and tutorials.
Nice and excellent Sir....got it...
Great explanation thank you sir..
Glad you liked it! Thank you very much. Keep watching and sharing.
WOW, very easy way explain
Could you please let me know which one should be written first - test plan or test strategy? I was asked this in an interview. I told "test plan is written first" which I think is wrong. Thank you.
Thanks a lot for this explanation
You are most welcome. Keep watching and sharing.
Thank u ...very clear and helpful
Just lot of love for what you are doing your points are very accurate and easy to understand thank u sir for eeverything🥰
Thanks, and welcome.
Keep watching for more videos and tutorials!
Thank you sir
thanks it is helpful
Glad it helped keep watching and sharing.
Sir Congrats! You have explained some very confusing terms in easy to understand manner. Thanks a ton!
Would you be creating a playlist on ISTQB Advanced certifications in the near future?
Thanks for this video sir 🙏
Most welcome! Keep Watching and Sharing.
Nice explanation
thank you.. this was really good
Well explained
Thank you.
Keep watching for more videos!
Merci beaucoup pour tes tutoriels!
Hi Mon, Thank you for your generous donation. Appreciate it! Regards, Manish
Superb explanation 👍
You have taken IBM. The IBM will be having many verticals which means they have a different strategies for every vertical. Then, the test plan is organised with the help of Test Architect for the Project. Lost! What are the various or set of Test Strategies IBM is having. Which are the Test Strategies used for BIMM tools like QIMM.
It's useful..thank you so much 🌻
Great explanation
Clearly explained!
Thank you 🙏
Loved it
Thanks.
Keep watching for more videos!
Awesoem thank you so much.Tomorrow is my ingterview, great help!!Genius you are
thanks
Sorry.. But
I tried to understand and revisited But still its so confusing.. The diagram is really not easy to go with.
Just one suggestion , when ever you are explaining things ,please don't cover the board . I'm not able to take the screenshot of these points.
Man! The whole time you are covering 20% of the board trying to jump into the frame. I can't see shit written on the left side. But that said, the explanation was great.
clearly explained. thanks
Glad it was helpful!