Test
Design, testing and IDEs
Este test tiene tipos de pregunta que se abren en el reproductor de siempre.
Preguntas del test (28)
15 reasons to use a structured diagram are coding is e[blank_start]asier[blank_end], each module can be written i[blank_start]ndependently[blank_end], easier to t[blank_start]est[blank_end], modules can be u[blank_start]pdated[blank_end] without affecting the whole thing and you can r[blank_start]euse[blank_end] the modules
- Aasier
- Bndependently
- Cest
- Dpdated
- Eeuse
24 features of maintainable source code is c[blank_start]omments[blank_end], good names for v[blank_start]ariables[blank_end], i[blank_start]ndentation[blank_end], and the use of s[blank_start]ub[blank_end] p[blank_start]rograms[blank_end]
- Aomments
- Bariables
- Cndentation
- Dub
- Erograms
3Input validation is where you check if d[blank_start]ata[blank_end] meets a c[blank_start]ertain[blank_end] c[blank_start]riteria[blank_end]
- Aertain
- Briteria
- Cata
4Range check checks if the d[blank_start]ata[blank_end] is within a r[blank_start]ange[blank_end]
- Aange
- Bata
5Presence check checks if d[blank_start]ata[blank_end] has been e[blank_start]ntered[blank_end]
- Aata
- Bntered
6Format check checks if d[blank_start]ata[blank_end] is the right f[blank_start]ormat[blank_end]
- Aormat
- Bata
7Look-up table checks if the d[blank_start]ata[blank_end] is in a t[blank_start]able[blank_end] of acceptable v[blank_start]alues[blank_end]
- Aable
- Balues
- Cata
8Length check checks if the d[blank_start]ata[blank_end] is the c[blank_start]orrect[blank_end] l[blank_start]ength[blank_end]
- Aength
- Borrect
- Cata
9Authentication is identifying the u[blank_start]ser[blank_end] to see if they are a[blank_start]llowed[blank_end] to access certain parts of the c[blank_start]ode[blank_end]
- Aode
- Bllowed
- Cser
10To make password-based authentication better, you can force users to have s[blank_start]trong[blank_end] p[blank_start]asswords[blank_end], limit the number of t[blank_start]ries[blank_end] they have and make them c[blank_start]hange[blank_end] their passwords r[blank_start]egularly[blank_end]
- Atrong
- Basswords
- Cries
- Dhange
- Eegularly
11A syntax error is when the t[blank_start]ranslator[blank_end] isn't able to u[blank_start]nderstand[blank_end] the code
- Aranslator
- Bnderstand
12A logic error is when the code r[blank_start]uns[blank_end], but doesn't have the correct [blank_start]response[blank_end]
- Aresponse
- Buns
13Logic errors are harder to f[blank_start]ind[blank_end] because the t[blank_start]ranslator[blank_end] won't identify it, you have to go through the code to f[blank_start]ind[blank_end] it yourself
- Aranslator
- Bind
- Cind
14Iterative testing is t[blank_start]esting[blank_end] during d[blank_start]evelopment[blank_end]
- Aevelopment
- Besting
15Final (terminal) testing is t[blank_start]esting[blank_end] that happens at the end of d[blank_start]evelopment[blank_end]
- Aevelopment
- Besting
16Normal data is the data l[blank_start]ikely[blank_end] to i[blank_start]nputted[blank_end]
- Aikely
- Bnputted
17Boundary data is the l[blank_start]imit[blank_end] the d[blank_start]ata[blank_end] can reach
- Aimit
- Bata
18Invalid data is the correct f[blank_start]ormat[blank_end] but still gets r[blank_start]ejected[blank_end]
- Aormat
- Bejected
19Erroneous data is the w[blank_start]rong[blank_end] data t[blank_start]ype[blank_end]
- Arong
- Bype
20Trace tables keep track of the v[blank_start]alues[blank_end] that certain v[blank_start]ariables[blank_end] take throughout the c[blank_start]ode[blank_end]
- Aariables
- Balues
- Code
21High-level language is easy to r[blank_start]ead[blank_end], one instruction could mean m[blank_start]ultiple[blank_end] ones, easily store d[blank_start]ata[blank_end], works for lots of different p[blank_start]rocessors[blank_end], must be t[blank_start]ranslated[blank_end] before and you don't have much c[blank_start]ontrol[blank_end] over what the C[blank_start]PU[blank_end] does
- Aead
- Bultiple
- Cata
- Drocessors
- Eranslated
- Fontrol
- GPU
22Low-level languages are harder to understand, one i[blank_start]nstruction[blank_end] usually means just one i[blank_start]nstruction[blank_end], written for just one p[blank_start]rocessor[blank_end], harder to store d[blank_start]ata[blank_end], more e[blank_start]fficient[blank_end] and f[blank_start]aster[blank_end], and doesn't need a t[blank_start]ranslator[blank_end]
- Aranslator
- Bfficient
- Caster
- Dnstruction
- Enstruction
- Frocessor
- Gata
23A compiler translates all the code at the s[blank_start]ame[blank_end] t[blank_start]ime[blank_end] and creates an e[blank_start]xecutable[blank_end] file, only needed once, returns a list of e[blank_start]rrors[blank_end] and once compiled it runs q[blank_start]uickly[blank_end] but compiling takes some t[blank_start]ime[blank_end]
- Aime
- Bame
- Cxecutable
- Drrors
- Euickly
- Fime
24An interpreter runs one i[blank_start]nstruction[blank_end] at a time, needed every time you r[blank_start]un[blank_end] the code, finds the first e[blank_start]rror[blank_end] and stops everything, and programs will run s[blank_start]lowly[blank_end] as each instruction must be t[blank_start]ranslated[blank_end] every time
- Aranslated
- Blowly
- Crror
- Dun
- Enstruction
25The code editor is where the code is w[blank_start]ritten[blank_end] and sometime has auto-i[blank_start]ndent[blank_end], auto-c[blank_start]olour[blank_end] c[blank_start]oding[blank_end], auto-c[blank_start]orrect[blank_end] and line n[blank_start]umbering[blank_end]
- Andent
- Boding
- Colour
- Dorrect
- Eumbering
- Fritten
26A run-time environment allows the program to be r[blank_start]un[blank_end] q[blank_start]uickly[blank_end] and helps to identifying [blank_start]logic[blank_end] errors
- Alogic
- Buickly
- Cun
27Error diagnostics helps to i[blank_start]dentify[blank_end] errors and ways of f[blank_start]ixing[blank_end] them
- Adentify
- Bixing
28Breakpoints stop the program at c[blank_start]ertain[blank_end] points so you can gather i[blank_start]nformation[blank_end] like the v[blank_start]ariables[blank_end]
- Aariables
- Bnformation
- Certain
Información
- Descripción
- GCSE Computing Test sobre Design, testing and IDEs, creado por Ben Rawlins el 23/04/2022.
- Autor
- Ben Rawlins
- Idioma
- English
- Visitas
- 0
- Etiquetas
- Valoración
- Aún sin valoraciones Valora este test