Test
Test Driven Development
Este test tiene tipos de pregunta que se abren en el reproductor de siempre.
Preguntas del test (14)
1Test driven development is an approach to program development in which you inter-leave [blank_start]testing[blank_end] and [blank_start]code[blank_end] development.
- Atesting
- Bcode
2Tests are written [blank_start]before[blank_end] code.
- Abefore
3Code is developed [blank_start]incrementally[blank_end], along with a [blank_start]test[blank_end] for that [blank_start]increment.[blank_end]
- Aincrementally
- Btest
- Cincrement.
4You [blank_start]do not[blank_end] move on to the next increment until the code that you have developed passes its [blank_start]test[blank_end].
- Ado not
- Btest
5Test driven development should start by identifying the [blank_start]increment[blank_end] of [blank_start]functionality[blank_end] that is required - it should be [blank_start]small[blank_end], and implementable in [blank_start]a few[blank_end] lines of code.
- Aincrement
- Bfunctionality
- Csmall
- Da few
6Next, a [blank_start]test[blank_end] should be written for this functionality, and implemented as an [blank_start]automated[blank_end] test.
- Atest
- Bautomated
7Run the test, along with [blank_start]all other[blank_end] tests that have been implemented. Initially you will not have implemented the functionality, so the test will [blank_start]fail[blank_end]. [blank_start]Implement[blank_end] the functionality and re-run the test. Once all tests run [blank_start]successfully[blank_end], you move on to implementing the next chunk of [blank_start]functionality[blank_end].
- Aall other
- Bfail
- CImplement
- Dsuccessfully
- Efunctionality
8The benefits of test driven development can be remembered by using the following acronym:
C[blank_start]ode coverage[blank_end]
R[blank_start]egression testing[blank_end]
S[blank_start]implified debugging[blank_end]
S[blank_start]ystem documentation[blank_end]- Aode coverage
- Begression testing
- Cimplified debugging
- Dystem documentation
9Code coverage: every code [blank_start]segment[blank_end] has been tested at least [blank_start]once[blank_end].
- Asegment
- Bonce
10Regression testing: a regression test [blank_start]suite[blank_end] is developed [blank_start]incrementally[blank_end] as a program develops.
- Asuite
- Bincrementally
11Simplified debugging: when a test fails, it should be [blank_start]obvious[blank_end] where the problem lies... in the newly [blank_start]implemented code[blank_end].
- Aobvious
- Bimplemented code
12System documentation: the [blank_start]tests[blank_end] are a form of documentation that describe what the [blank_start]code[blank_end] should be doing.
- Atests
- Bcode
13Regression testing is testing the system to check that changes have not [blank_start]broken[blank_end] previously [blank_start]working[blank_end] code.
- Aworking
- Bbroken
14In a normal testing process, regression testing is [blank_start]expensive[blank_end], but with [blank_start]automated[blank_end] testing, it is [blank_start]simple[blank_end] and [blank_start]straightforward[blank_end].
- Aexpensive
- Bautomated
- Csimple
- Dstraightforward
Información
- Descripción
- Games Development Test sobre Test Driven Development, creado por Kerrie Callaghan el 08/05/2017.
- Autor
- Kerrie Callaghan
- Idioma
- English
- Visitas
- 0
- Etiquetas
- Valoración
- Aún sin valoraciones Valora este test