¡GoConqr estrena diseño! Cuéntanos qué te parece.

Test

Seven principles of software testing

Kerrie Callaghan 8 preguntas Actualizado el 8 may 2017

Hacer el test

Este test tiene tipos de pregunta que se abren en el reproductor de siempre.

Preguntas del test (8)

  1. 1What are the seven principles of software testing?
    P[blank_start]resence of errors[blank_end]
    E[blank_start]xhaustive testing is impossible[blank_end]
    E[blank_start]arly testing[blank_end]
    D[blank_start]efect clustering[blank_end]
    C[blank_start]ontext dependent[blank_end]
    A[blank_start]bsence of errors fallacy[blank_end]
    P[blank_start]esticide paradox[blank_end]
    1. Aresence of errors
    2. Bxhaustive testing is impossible
    3. Carly testing
    4. Defect clustering
    5. Eontext dependent
    6. Fbsence of errors fallacy
    7. Gesticide paradox
  2. 2Presence of errors: testing can show that defects are [blank_start]present[blank_end], but cannot prove there are [blank_start]no defects[blank_end].
    1. Apresent
    2. Bno defects
  3. 3Exhaustive testing is impossible: testing [blank_start]everything[blank_end] (all combinations of [blank_start]inputs[blank_end] and [blank_start]preconditions[blank_end]) is not feasible. Instead of exhaustive testing, [blank_start]risk[blank_end] analysis and [blank_start]priorities[blank_end] should be used to focus testing efforts.
    1. Aeverything
    2. Binputs
    3. Cpreconditions
    4. Drisk
    5. Epriorities
  4. 4Early testing: to find defects [blank_start]early[blank_end], testing activities shall be started [blank_start]as early as possible[blank_end] in the SDLC.
    1. Aearly
    2. Bas early as possible
  5. 5Defect clustering: a [blank_start]small[blank_end] number of [blank_start]modules[blank_end] usually contains [blank_start]most[blank_end] of the defects discovered during [blank_start]pre-release[blank_end] testing.
    1. Asmall
    2. Bmodules
    3. Cmost
    4. Dpre-release
  6. 6Pesticide paradox: if the same test cases are [blank_start]repeated[blank_end] over and over again, eventually the same tests will [blank_start]no longer[blank_end] find new defects. To combat this, test cases must be regularly [blank_start]reviewed[blank_end] and [blank_start]revised[blank_end].
    1. Arepeated
    2. Bno longer
    3. Creviewed
    4. Drevised
  7. 7Testing is context dependent: testing is done [blank_start]differently[blank_end] in [blank_start]different contexts[blank_end]. For example, safety critical software is [blank_start]tested differently[blank_end] to an e-commerce site.
    1. Adifferently
    2. Bdifferent contexts
    3. Ctested differently
  8. 8Absence of errors fallacy: finding and fixing errors [blank_start]does not[blank_end] help if the system built is [blank_start]unusable[blank_end] and does not fulfill the users [blank_start]needs[blank_end] and [blank_start]expectations[blank_end].
    1. Adoes not
    2. Bunusable
    3. Cneeds
    4. Dexpectations

Información

Descripción
Games Development Test sobre Seven principles of software testing, creado por Kerrie Callaghan el 08/05/2017.
Idioma
English
Visitas
0
Historial
Creado el 8 may 2017 · actualizado el 8 may 2017
Etiquetas
games development
Valoración
Aún sin valoraciones
Valora este test
Valora este test

Escríbenos

¿Sobre qué es tu mensaje?

¿Qué te parece el nuevo diseño?

¿Te gusta?