Test
Tutorial 7
Este test tiene tipos de pregunta que se abren en el reproductor de siempre.
Preguntas del test (19)
1The Microservices Architecture is a variant of the [blank_start]Service[blank_end] [blank_start]Oriented[blank_end] [blank_start]Architecture[blank_end] architectural style that structures an application as a collection of [blank_start]loosely[blank_end] coupled services
- AService
- BOriented
- CArchitecture
- Dloosely
2Fill in the blanks.
- Amonolithic
- Bmicroservices
3Services also rely more on well [blank_start]documented[blank_end] interfaces, promoting better encapsulation and so reduced [blank_start]coupling[blank_end]
- Adocumented
- Bcoupling
4In black box testing, we design test cases by looking at the s[blank_start]pecification[blank_end] (that is, [blank_start]requirements[blank_end] and [blank_start]high[blank_end]-[blank_start]level[blank_end] [blank_start]design[blank_end]) of the system to be tested.
In white box testing, we design test cases by looking at the [blank_start]detail[blank_end] of the i[blank_start]mplementation[blank_end] of the system to be tested.- Apecification
- Brequirements
- Chigh
- Dlevel
- Edesign
- Fdetail
- Gmplementation
5What are two techniques of black-box testing?
- Aequivalence class
- Btesting with Design By Contract
- CCyclomatic complexity
- DCoupling-Between-Objects (CBO)
6Equivalence classes are groups of possible [blank_start]inputs[blank_end] that the system should treat [blank_start]similarly[blank_end].
- Ainputs
- Bsimilarly
7Using equivalence classes, testers need only to run the following tests:
- Aone test per equivalence class using a
representative member of that class - Bone test at the boundaries of the equivalence class
- Cseveral tests using random values within the equivalence class
- Dseveral tests around the boundaries of the equivalence class
- Aone test per equivalence class using a
8Example of Equivalence Class values
- Aok
- Bnot ok
9In black-box testing with Design By Contract, we test the [blank_start]post[blank_end]-[blank_start]condition[blank_end].
- Apost
- Bcondition
10The number of white-box tests is determined by
the [blank_start]cyclomatic[blank_end] [blank_start]complexity[blank_end] of the code- Acyclomatic
- Bcomplexity
11Cyclomatic complexity count starts from [blank_start]1[blank_end] as it represents a ‘straight-through’ path. Decision points are the following statements in code:
• if, while and do-while loop, for loops - all have the value [blank_start]1[blank_end] (use the number).
• catch-try - have the value [blank_start]1[blank_end](use the number) per catch block
• switch - have the value 1 per [blank_start]case[blank_end]
• statements such as while(true) are [blank_start]not[blank_end] [blank_start]counted[blank_end]
- A1
- B1
- C1
- Dcase
- Enot
- Fcounted
12If our cyclomatic complexity was high then it would suggest
that it would be better to [blank_start]split[blank_end] code into [blank_start]separate[blank_end] methods.
- Asplit
- Bseparate
13Which of the following statements are true about software metrics?
- ADepth-of-Inheritance-Tree (DIT) is the number of hops from a class up its inheritance tree.
- BCoupling-between-objects (CBO) is the number of relationships the class has with other classes
- CResponse-for-a-class (RFC) is the number of methods of a class including inherited and other methods called
- DCoupling-between-objects (CBO) is the number of methods of a class including inherited and other methods called
- EResponse-for-a-class (RFC) is the number of hops from a class up its inheritance tree.
14Depth-of-Inheritance-Tree (DIT) is the maximum length from the [blank_start]node[blank_end] to the [blank_start]root[blank_end] of the tree. We start with [blank_start]0[blank_end] (number) and add [blank_start]1[blank_end] (number) per hop.
- Anode
- Broot
- C0
- D1
15Which of the below statements apply to Depth-of-Inheritance-Tree (DIT)?
- AThe deeper a class is in the hierarchy, the greater
the number of methods it is likely to inherit,
making it more complex to predict its behaviour. - BThe deeper a class is in the hierarchy, the greater
the number of methods it is likely to inherit,
making it easier to understand as fewer methods are defined in the class. - CDeeper trees constitute greater design complexity
- DDeeper trees constitute lesser design complexity
- AThe deeper a class is in the hierarchy, the greater
16Coupling-Between-Objects (CBO) is defined as the number
of [blank_start]relationships[blank_end] the class has with other classes. The more it has, the more difficult it is to understand the [blank_start]use[blank_end] of the given class.
- Arelationships
- Buse
17Select all statements that apply to Coupling-Between-Objects (CBO). Select 3.
- AHigh CBO makes the code harder to reuse
- BHigh CBO means class definitions will be shorter and therefore easier to understand
- CHigh CBO means alterations to a code in one are runs a high risk of affecting code in other areas
- DHigh CBO makes it impossible to test the code
- EThe more links between classes the more difficult it will be to test
18It is the number of [blank_start]methods[blank_end] (including [blank_start]inherited[blank_end] ones and the [blank_start]constructor[blank_end]) of the class plus the number of methods [blank_start]called[blank_end] by any of those.
- Amethods
- Binherited
- Cconstructor
- Dcalled
19Select all that apply to Response-for-a-class (RFC). Select 2.
- AHigh RFAC makes testing and debugging much harder
- BLow RFAC makes testing and debugging much harder
- CThe more methods a class invokes, the greater the complexity of the class
- DThe more methods a class invokes, the more cohesive it is
Información
- Descripción
- Software Engineering Test sobre Tutorial 7, creado por Frans k el 01/05/2018.
- Autor
- Frans k
- Idioma
- English
- Visitas
- 0
- Etiquetas
- Valoración
- Aún sin valoraciones Valora este test