A Practical Approach to Risk-based Testing

This course is an introduction to how risk management is applied to testing. It tries to show how these risks can be actually used to improve and focus strategies when testing a software product.


In the course we’ll see how risks define type and scale of the tests to run. We’ll see the ways in which a testing team must report risks in each stage of a project, so that managers can evaluate client deadlines. Likewise, we’ll also discuss case studies that illustrate a fair balance between project risks (to complete all tests on time) and product risks (what happens if the flawed product is shipped).

Testing resources are generally scarce and follow restriction-based management. Restrictions imply risks. Most of the time the best strategy is to focus on what could go wrong instead of trying to cover the project’s entire scope. When we talk about risk-based testing management, it’s important to know what elements must be monitored: severity and quantity of the identified bugs, identification / correction ratio, coverage, etc.

During the course we’ll go over some key metrics to carry out a risk-based testing strategy. We’ll also look into different analysis and evaluation techniques for each product and project, based on real-life scenarios. We’ll also show you how to evaluate developer build quality, how to look beyond release notes and how to analyze the impact of corrections and changes throughout the software’s life cycle.

Towards the end of this course we will give you the chance to apply what you’ve learned within new development and system maintenance contexts.

Duration: 2 to 4 days / 16 hours


This course is face-to-face and will consist of four, six or eight-hour classes.


This course is targeted at people who take part in software testing processes. We recommend that you already have a grasp on project management and have actively participated in testing projects.


This course focuses on learning to identify and prioritize risk in order to develop an accurate testing strategy that lets the testing team provide the information that management needs to take informed decisions.

  • To describe the concepts and principles behind risks involved in building or maintaining software, and how they relate to testing.
  • To apply a practical approach to the risk-based testing method
  • To plan and manage a practical risk evaluation using both “formal” and “agile” project techniques.
  • To learn to manage human psychological biases within the team analyzing risks
  • To develop a risk-based testing strategy
  • To effectively monitor and communicate project risks and to provide support in product shipping decisions.


Introduction to risk management

What is risk?

Risk in processes, products and projects

Testing and risks: some hard questions

How much testing is enough?

When do we stop testing?

When is the product good enough?

Risk identification techniques

Expert interviews

Expert evaluations

Learned lessons

Common risk checklist

Risk workshops

Risk analysis

Techniques to evaluate the impact and probability of risks

Qualitative evaluations versus quantitative evaluations

Developing a risk-based testing strategy

Identifying product risks; quadrant use

Different points of view and psychological factors

Using risk analysis to focus and prioritize testing

Using risk to define testing objectives

The perfect balance between estimates and plans

Risk-based case design and execution

Tracking risks and tests

Prioritizing the testing schedule

Notions in risk-based testing management

Risk analysis and identification

Defining a plan that responds to risks

Risk monitoring: why should we monitor?

Adapting strategies and plans to monitoring results

Examples of metrics and report techniques

The shipping decision

Who takes the shipping decision?

What information does one need to make an informed decision?

Testing quantification

Coverage – have we made sufficient tests?

What risks does the shipped software have?

Case study discussion

Risk-based testing management in software development projects

Risk-based testing management in product maintenance


ISTQB Foundation Level


Participants must have basic knowledge or experience in IT projects


A Practical Approach to Acceptance Testing

This course covers every aspect of user acceptance testing, from defining objectives to producing the scripts needed to run the tests.


The course is set out like a workshop, using real-life case studies as examples, apart from some reference material. Likewise, group discussions are encouraged as the way to grasp the concepts conveyed.

The course’s format makes it easily adaptable to all of the participants’ needs without jeopardizing the learning process. For instance, one of the first problems we tackle is how to determine if a system’s requirements are complete and correctly understood by everyone involved in the business.

Duration: 2 to 4 days / 16 hours


This course is face-to-face and will consist of four, six or eight hour classes.


This course is targeted at every person that takes part in user acceptance testing processes. We welcome both testers and business stakeholders alike.


Throughout the course participants will go through all user acceptance testing stages, using a real-life case study.

  • To understand the purpose of user acceptance testing and how business objectives are fit into system requirements.
  • To learn how to check system requirements in order to guarantee that the right system will be built, in the right way
  • To see how requirements are used to build realistic acceptance criteria for the system.
  • To understand the practical use of business risk analysis when working with a system that works incorrectly and to focus all testing efforts on the results of that evaluation.
  • To identify important business processes that must be verified by acceptance tests
  • To use scenarios to determine test conditions and objectives.
  • To use test design techniques to build acceptance test scripts.
  • To plan the project’s test execution stage and build the acceptance test schedule.
  • To manage the execution stage and correctly identify when testing is finally done.


Introduction to user acceptance tests

Reviewing requirements and defining acceptance criteria

Evaluating business risks

Identifying test scenarios

Writing test conditions

Building test scripts

Creating a test schedule

Managing the test execution stage


Participants must have basic knowledge or experience in IT projects. The only previous reading required is the course’s program.

Volver arriba

ISTQB Foundations Course

This course is the first stepping stone in the international "Certified Tester Foundation Level Certificate in Software Testing" certification and follows the "Certified Tester Foundation Level" program from the International Software Testing Qualifications Board (ISTQB).


The course covers the ISTQB Foundation level study program completely, using official training materials in Spanish. This course enables those who wish to continue with their ISTQB software testing certifications career to sit for their “Certified Tester Foundation Level Certificate in Software Testing” exam.

Generalmente los recursos para el testing son escasos, y se gestionan en base a restricciones. Las restricciones implican riesgos. Muchas veces la mejor estrategia es la que enfoca en aquellas cosas que pueden funcionar mal, pues aquella que garantiza la mayor cobertura no es posible en las circunstancias del proyecto. Cuando hablamos de gestionar el testing en base a riesgos, es muy importante conocer qué elementos deben ser monitoreados: cantidad y severidad de bugs identificados, ratio de identificación / corrección, cobertura, etc.

Se revisarán durante el curso las métricas clave para una estrategia de pruebas basada en riesgos. Se revisarán también técnicas de análisis y evaluación de riesgos relativos al producto y al proyecto, basados en casos prácticos. Observaremos cómo evaluar la calidad de los builds de desarrollo, cómo mirar más allá de las release notes, y cómo realizar el análisis de impacto de las correcciones y cambios a lo largo del ciclo de vida del producto de software.

Sobre el final del curso, se revisará la aplicación de los conocimientos adquiridos en el contexto de desarrollo nuevo y de mantenimiento de sistemas en producción.

Duration: 3 days / 24 hours


The course consists of three face-to-face, eight-hour classes, with a lunch break at noon.


This basic-level certification is ideal for all software testing professionals: testers, test analysts, users involved in acceptance tests and software developers. There are no pre-requisites and is therefore also suitable to anyone looking to grasp a basic understanding of the software testing process. This includes project managers, QA professionals, team and development leaders, business analysts and consultants.


  • To prepare participants at an international level, recognized by employers, clients and peers;
  • To understand the basic principles behind software testing and the testing process;
  • To impart formal knowledge about the basic testing techniques (static, white box, black box) and to share practical experience on those usually used;
  • To bring participants closer to the standard software testing terminology;
  • To provide a complete vision of all software testing-related activities and processes, from requirement analysis to system implementation;
  • To understand testing management as a fundamental process within the development cycle.


Software testing fundamentals

Why do we need to test?

What is testing? General principles behind software tests

Testing process fundamentals

Psychology of testing

Testing along the life cycle

Software development models

Test levels

Test types

Testing objectives

Testing in maintenance projects

Static techniques

Revisions and testing processes

Revision process

Static analysis with tools

Test design techniques

Identifying test conditions and test case design

Categories of design techniques

Design based on specifications or “black-box techniques”

Design based on architecture or “white-box techniques”

Design based on experience

How to choose design techniques

Test management

Testing organization

Test planning and estimates

Progress control and monitoring

Configuration management

Risks and tests

Incident management

Supporting tools

Types of supporting tools

Effective usage of tools

Uses and potential benefits

Introduction to tools in the organization


Participants must have basic knowledge or experience in IT projects. The only previous reading required is the course’s program.

If you're interested, please click here, fill out the form and we'll get back to you shortly.

Copy by Les Mots.