ISTQB Software Certification Studyguide

1. Planning and control
2. Analysis and design
3. Implementation and execution
4. Evaluating exit criteria and reporting
5. Test closure activities

This testing process begins at the start of the project, during the requirements stage, and continues throughout. Your goal is to:

• establish the mission for testing,
• define the objectives of testing and
• describe the test activities and the testing tasks to meet the mission and the objectives.

Start by writing a plan describing the test strategy for the project.

The test activities and tasks for one or more testing projects.

In in the planning phase.

1. Identifying goals, risks, scope and high-level test objectives
2. Determining the test approach
3. Identifying and interfacing with the teams involved in development and testing
4. Determining the required test resources
5. Implementing the organization’s test policy
6. Scheduling test analysis and test design tasks
7. Scheduling test implementation, execution, and evaluation
8. Determining the exit criteria

Decide what to test and not test because everything cannot be tested.

What are the goals, risks, the priorities and the high-level test objectives?

What techniques will you use? How will you document test designs and report testing activities and results? What measurements will you make, record, publish, and save? What artifacts or testware will you create for reuse later?

Identify the programmers and the process model they follow and the tools they use.
Determine if testers will have access to everything needed from development and testing.
Identify the stakeholders, third-parties, out-source services etc that may affect our testing decisions.

How many testers will be needed and for how long? What type of test environment is needed to resemble the production environment as closely as possible? What testing tools are needed?

How will you use your company’s overall testing or quality assurance (QA) policies to evaluate the software?

Test designs and test cases should be built based on the requirements. Are you involved in the requirements process? How can you get involved? Should some tests be automated? How will you determine if tests pass or fail? Can you influence the software’s design to make testing more efficient?

When will these activities take place? Can you test portions of the product before everything is ready? Who will execute the tests? What tests can be automated and how? How are incidents reported? How are defects prioritized for correction and tracking for retesting?

How will you know when to stop testing? What will be the exit criteria for testing? How will you report status and recommendations to stakeholders?