Test Management – Chapter 5 – ISTQB Foundation

The fifth part of the series of summaries to help you with the ISTQB exam certification. This will help you memorize what is going to be likely to be on the exam questions. Every little information helps with the exam for the ISTQB certification foundation level I hope you make the most of this series.

Read, then practice the exam for the chapter 5 – Test Management, link at the end of this summary, practice the quiz as much as you like or until you feel comfortable enough to go to the next chapter.

If you feel that you are ok to try the actual exam, there’s a quiz for that as well next to the chapter five.

More you read, more you understand, more you understand more you are ready to sit at the exam.

I have uploaded a mind map with a graphical visualization of the ISTQB Foundation Level topics, a kind of Cheat Cheat, you may find it useful too to help you with the exam.

Hope you like. Feel free to drop me a comment, or inform anything that I’ve missed here. Good luck.

Risk

A factor that could result in future negative consequences

Level of risk

Probability of risk occurring x impact if it did happen

Project risks

Supplier issues, skill or staff shortage, personal issues, requirement issues, test environments not ready, low quality of design, code, and tests

Product risks

Failure prone software delivered, potential for a defect to cause harm, poor software characteristics, software that doesn’t do what it is supposed to

Risk-based testing

Proactively reduces the risk by identifying them and mitigating them as soon as possible

Risk-based approach

  • Determines test techniques and the extent of testing needed
  • Prioritize testing in an attempt to find critical defects as early as possible
  • Determines non-testing techniques that could reduce risk

Test leader tasks

  • Coordinating the development of the test strategy and plan with project managers
  • Writing or reviewing test strategies
  • Contributing testing perspective to other project activities
  • Planning the development of the required tests
  • Taking required action on issues
  • Scheduling testing activities

Tester tasks

  • Reviewing and contributing to development of test plans
  • Analyzing, reviewing, and assessing user requirements
  • Creating test specifications
  • Setting up the test environment
  • Implementing tests
  • Monitoring and reviewing tests

Test approach

All of the decisions made on how testing should be implemented, based upon project goals and risk assessment

Factors for selecting a test approach

  • Risk of failure of the project
  • Skills and experience of the people in the proposed techniques, tools, and methods
  • Object and mission of the testing team
  • Regulatory aspects
  • Nature of the product and business

Master test plan

Main document produced in testing which details each of the other test plans

IEEE 829

Standard for Software Test Documentation

16 sections of IEEE 829

S – scope
P – people
A – approach
C – criteria
E – environment needs
D – deliverable (test)
I – identifier and introduction
R – risks and contingencies
T – testing tasks and schedule

Test planning activities

  • Working with the project manager and SMEs to determine the scope and risks
  • Putting together the test strategy
  • Liaising with the project
  • Working with the project to decide what needs to be tested
  • Building a plan that identifies when and who will do the test analysis and design
  • Finding and assigning resources
  • Deciding what docs will be needed
  • Ensuring test documentation generates repeatable test assets

Entry criteria

Determines when a test activity can start

Exit criteria

Determines when a given test activity has been completed or when it should stop

Two approaches of test estimation

Metrics-based approach and expert-based approach

Metrics-based approach test estimation

Estimates the cost and time of a project based on metrics from previous or similar projects

Expert-based approach test estimation

Estimates the cost and time of a project based on the experiences of the task owners

Common metrics to measure test progress

  • Percentage of work done in test case prep
  • Percentage of work done in test environment preparation
  • Number of tests run/not run
  • Test coverage
  • Dates of milestones

Test control

The activity of using information from test reporting to decide on a course of action to ensure control of the test activities is maintained and exit criteria are met


Rogerio da Silva

Test Analyst (ISTQB-ISEB Certified Tester) | Test Lead | Business Test Analyst | Entrepreneur | Investor Share, Stocks, Forex and Cryptocurrency | Social Media Marketing | Social Media Management | Website Consulting & Revision | Email Consulting (Funnel Setup) Rogerio da Silva is a Consultant as a day job and big fan of personal development and entrepreneurship. Feel free to follow him on LinkedIn, Twitter, Facebook Page, Tumblr, Google+ to talk about ideas, investments, business opportunities in UK and Brazil.

Leave a Reply

%d bloggers like this: