Fichas
F452 testing methods
Fichas del conjunto (5)
- 1Black box testingConducted after main development, real inputs are tested against their expected outcomes, without any knowledge of the code or considering how the program works.
- 2White box testingConducted during development, all paths through an algorithm need to be tested to ensure that all steps work as intended. Code is visible and known to the tester and actual steps of the algorithm are tested.
- 3Alpha testingCarried out by programmer, during development, playing role of the user to find any bugs or glitches in the system.
- 4Beta testingConducted by a small group of future users, when the program is almost complete to find any undiscovered bugs or glitches.
- 5Acceptance testingAfter development is complete, but before handing it over, the program is tested to prove to the end user that the program works properly and meets the design objectives.
Información
- Descripción
- A level Computing Fichas sobre F452 testing methods, creado por Joseph Stevens el 23/04/2015.
- Creado por
- Joseph Stevens
- Visitas
- 6
- Etiquetas
- Valoración