ISTQB - Test Management

Test Organization

• Test Organization is about who does the testing and how the team is structured.

Roles

• Different roles such as testers and test leads are defined based on skills and responsibilities.

Independence

• Sometimes, testers are independent of developers to ensure unbiased testing.

Example

• In a project, you might have a test team separate from the development team. Each person has a specific role like writing test cases or analyzing results.

Test Planning and Estimation

Goals

• This is about planning the testing activities and estimating how long and how much effort testing will take.
• Deciding what to test, how to test it, and what resources such as time, people, and tools are needed.
• Predicting how long the testing will take using techniques like past experience or simple math based on tasks.

Example

• Imagine planning to test a website. You decide you need: 2 weeks, 3 testers, and specific tools to check browser compatibility.

Test Monitoring and Control

Goals

• This refers to tracking how testing is going and making adjustments if needed.

• Keeping track of what’s been tested, what issues were found, and how much time remains.

• If something is going wrong for instance delays, you take steps to fix it, by adding more testers to speed up the testing.

Example

• Halfway through the project, you notice that testing is behind schedule, so you might bring in more testers or reduce the scope of testing.

Configuration Management

Goals

• This ensures that the correct versions of software, test cases, and documents are used.

• It helps in tracking changes and making sure everyone is working with the right files, versions, and settings.

Example

• You want to make sure that when a bug is fixed, the exact version of the software with the fix is tested, not an outdated or incorrect version.

Risk and Testing

• Testing is used to reduce risks in the software. It involves identifying what could go wrong and focusing testing on those risky areas.

Risk-based testing

• If certain parts of the system are more likely to fail or have a bigger impact, you test them more thoroughly.

Example

• If you’re testing an e-commerce site, payment processing is a high-risk area, so you’d spend more time testing that than something less critical like the contact form.

Module Review

Click to start the definition to term matching quiz

Drag the defintion to the correct term.

Open the defintion to term matching quiz

Click to start the multiple choice quiz

Choose from the listed options below.

Score: : 0 / 12 [0.00 %]

Question 1 of 12: What is the purpose of Test Planning and Estimation?