| Channel | Publish Date | Thumbnail & View Count | Download Video |
|---|---|---|---|
 | Publish Date not found |  0 Views |
Difference between test plan and test strategy
Possible interview questions about testing strategy
Test strategy
Test strategy is a guideline that must be followed to achieve the test objective and execute the types of tests mentioned in the test plan. It deals with test objective, test environment, test approach, automation tools and strategy, contingency plan and risk analysis.
Defines the strategic plan for conducting tests on one or more aspects of the target system.
The testing strategy includes:
1. Scope and objective:
The business objective and how much testing scope there will be for the product in the testing strategy.
It specifies which test engineer must review which test documents and which test activities must be carried out within a certain period of time.
2. Business problems:
What is the project budget, how much time is needed for testing, how many resources are needed, etc. – these are business questions that need to be considered before actually testing.
3. Test approach:
What type of testing is required (performance, load, stress, functional, etc.). Roles and responsibilities of a particular test engineer. Testing processes and whether the testing will be done manually or automated or both are some of the crucial points that define the testing approach.
4. Test results:
Here you will learn what documents are required by the testing team, how they maintain records of test cycles, etc.
5. Approach to bug tracking:
At this point in the test strategy, decisions are made about which defect tracking tool will be used, how the test team will communicate with the development team, and what the defect handling process will be.
6. Automation:
If the project or company requires automation testing, the test strategy plans the scripting language, the tool used, reporting, and the code maintained.
7. Risks:
No one can foresee all risks in advance, but obvious risks can be avoided and solutions (if risks arise) can also be included in the document for future assistance.
Difference between test plan and test strategy.
Test plan test strategy
1) The test plan is a document that controls all future testing activities.
1) The test strategy is a guideline that must be followed to achieve the test objective and execute the types of tests specified in the test plan.
2) The test plan is implemented by a test manager or leader who describes how testing will be done, when testing will be done, who is testing and what is being tested
2) The test plan is implemented by a test manager or leader who describes how testing will be done, when testing will be done, who is testing and what is being tested
3) A test plan defines the strategy used to verify and ensure that a product or system meets its design specifications and other requirements.
3) The test strategy is a blueprint that describes the testing approach of the software development cycle.
4) The test plan may change
4) Test strategy cannot be changed
5) It is defined at project level
5) It is defined at the organizational level and can be used by multiple projects
Possible interview questions about testing strategy
What is test strategy?
What are the test strategy approaches
What are the differences between test plan and test strategy?
ankpro
ankpro training
ASP.NET MVC
C#
C sharp
Bangalore
Rajajinagar
selenium
Coded user interface
Mobile automation testing
Mobile testing
jQuery
JavaScript
.Network
C
C++
Components of the .Net Framework
Hello World
Literally
keywords
variable
Data types
operator
branch
Grind
Arrays
Strings
Buildings
Lists
Features
Please take the opportunity to connect with your friends and family and share this video with them if you find it useful.
