Software testing risks

Introduction

Risk is something that can happen and lead to negative consequences

Interesting point: sometimes we can do nothing with risk or our effects are not enough to eliminate risk from the list. Systemic risks can not be completely excluded, as are often a feature of the process in which we work.

In this video file, you can find a great team-work example with risks analysis in the software development cycle:

example

  1. Not a bug

How to prevent it?

if you are found an issue that may look like a bug, you must continue with these steps:

  1. You must reproduce it
  2. View the test task (Story)
  3. Bug localization (minimum reproducing steps)

Create a Bug report

  1. With Confluence descriptions link
  2. Requirements
  3. Client documentation
  4. Design (wireframes, mockups)
  5. Logs
  6. Screenshots/Video

Risk management activities are cyclical, like any other project activities, if you work in iterations. At the same time, if the iterations are long enough, the work cycles associated with risk management can be several.

An algorithm of working with risks can be presented:

  1. detection
  2. analysis and prioritization
  3. planning
  4. monitoring and reporting
  5. adjustment
  6. findings

Reference

  1. Павла Толоконина, Позитивные и негативные риски на проекте (2017)
  2. Андрей Кулешов, О записи багов, или Найди кота (2019)

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store