Difference between test plan and test strategy
Test plan vs. test strategy

In this video ️
Test strategy:
It is a document and defined at organizational level
. It is a vision of testing. It defines test objectives, general testing approaches (Manual Automation API), test data (dummy data or production data as per company guidelines), test tools, environment, defect management process, test metrics, risk analysis and mitigation, and reporting at organization level.
The testing strategy does not usually change frequently

Experimental plan:
It is a document and defined at project level
. It is a blueprint or guideline that describes the test scope, test approach (manual or automated), test types (functional, non-functional, integration, smoke, regression, etc.), resources, test coverage scenarios (agile), exit criteria, test results, and planning of planned test activities during a project. In fact, it is a template to inform other stakeholders about what the test team is doing and how it is performing on a particular project.
. The test plan may change over time as the project is updated.

Test plan vs. test strategy document: https://codenboxautomationlab.com/test-plan-test-strategy-for-amazon-ca/

usefull links
Blog http://codenboxautomationlab.com/​​
GitHub repo https://github.com/codenbox​​/

connect with us
Facebook: https://www.facebook.com/CodenBoxQA/​​
Twitter: https://twitter.com/CodenboxTeam
LinkedIn: https://www.linkedin.com/in/sarifuli/

Please click “Like️” and SUBSCRIBE for more AWESOME content!

Please take the opportunity to connect with your friends and family and share this video with them if you find it useful.