Test Plan Vs Test Strategy || Difference between Test Plan & Test Strategy
+Difference between Test Plan & Test Strategy
+Test Plan Vs Test Strategy
▬▬▬▬▬▬ In this Video ▶️ ▬▬▬▬▬▬
Test Strategy:
. It’s a document and defines at Organization level
. It’s a vision of Testing. It defines test objectives, general Test approaches (Manual +Automation+API), Test data( Dummy data or production data following companies guide line), Testing tools , Environment , Defect management Process , Test metrics, Risks analysis and mitigation & Reporting at Org level.
. Test Strategy usually doesn’t change frequently
Test Plan:
. It’s a document and defines at project level
. It’s a blueprint or guideline that describes Test scope, Test approach (Manual or automation), Testing Types, (functional, Non-functional, Integration, Smoke, Regression etc), Resources, Scenarios for test coverage (Agile), Exit Criteria, Test deliverables and scheduling to intend testing activities during a project level. In fact, it is a template to let other stakeholders know what the Testing team is doing & how they are doing for a specific project
. Test plan can change over time as the project gets updated.
👉 Test Plan Vs Test Strategy Doc: https://codenboxautomationlab.com/tes...
▬▬▬▬▬▬ Useful Links 🛠 ▬▬▬▬▬▬
Blog ► http://codenboxautomationlab.com/
GitHub Repo ► https://github.com/codenbox/
▬▬▬▬▬▬ Connect with us 👋 ▬▬▬▬▬▬
💻 Facebook: /
📱 Twitter: / codenboxteam
📝 LinkedIn: / sarifuli
🌟 Please hit on LIKE ❤️ and SUBSCRIBE for more AMAZING content! 🌟
