Aún no tienes acceso a esta clase

Crea una cuenta y continúa viendo este curso

Handle bugs to fit your process

23/27
Recursos

In this lesson you will understand: The lifecycle of a Bug. Continuous Delivery. Spike Test. Estimate bug fixing effort

Challenge: using your knowledge of Bug Handling, answer this multiple choice activity

Aportes 5

Preguntas 2

Ordenar por:

¿Quieres ver más aportes, preguntas y respuestas de la comunidad? Crea una cuenta o inicia sesión.

I’m not pretty sure about the estimation formula due to it depends on the bug, because there must be other variables, such as priority, or impact.

There are other methods to calculate that estimation?

Continuous delivery - fix functional bugs
- Create stories to fix bugs
- Take into consideration when estimating time
- First fix functional bugs
- Everything revolver about customer-oriented functionality

Estimate bug-fixing effort
Spike test
- Period in which there is an “explosion” in the testing activities
- Random and continuous
- Weed out bugs
- Take a week to do it
- Pick a random sample of test that are failing and try to fix them
- Estimate bug fix rate

-Spike test
Spike testing is a period in which
there is an “explosion” in the
testing activities.
Test continuously, take random
bits of code and functionalities
to ensure functionality before
delivery.

-Spike test
Weed out bugs, later you can use the results to estimate
adjustments.

  1. Take a week to do your spike test
  2. Pick a random sample from the tests that are failing and try
    to fix just those tests.
    Act based on the results of the Spike testing effort. At the end of
    the week calculate your bug fix rate.
    Fix functionality only

Spike testing = is test type oriented to the app receives a sudden and extreme increase a decrease in load, this for determinate the behavior of the app when it receives extreme variations in traffic.

Bug Fix
Rate (BFR)