40 Questions Quiz 9 (321-360)

Question

What is failure?

Answer 1

A. Deviation from expected result to actual result

Answer 2

B. Defect in the software.

Answer 3

C. Error in the program code.

Answer 4

D. Fault in the system.

Answer 5

A. Static analysis tool

Answer 6

B. Performance testing tool

Answer 7

C. Test comparator

Answer 8

D. Test management tool

Answer 9

A. Estimating test duration.

Answer 10

B. Incident Management.

Answer 11

C. Configuration Management.

Answer 12

D. De-bugging.

Answer 13

A. IEEE 802.11

Answer 14

B. ISO 9001

Answer 15

C. BS 7925-1

Answer 16

D. BS 7925-2

Answer 17

A. Use of automated test execution tools.

Answer 18

B. Testing performed by users.

Answer 19

C. Testing against acceptance test criteria.

Answer 20

D. Integration of system with user documentation.

Answer 21

A. Test management

Answer 22

B. Test design

Answer 23

C. Test planning

Answer 24

D. Test execution

Answer 25

A. Regression testing.

Answer 26

B. Integration testing.

Answer 27

C. Error Guessing

Answer 28

D. System testing.

Answer 29

A. It is easy to execute.

Answer 30

B. It is designed to detect faults if present.

Answer 31

C. The expected outcome is specified before execution.

Answer 32

D. It is unlikely to delay progress.

Answer 33

A. An appropriate way of deriving system tests.

Answer 34

B. Only used if good requirements are not available.

Answer 35

C. Only used when good requirements are available.

Answer 36

D. The most appropriate way of deriving system tests.

Answer 37

A. Risks involved

Answer 38

B. Contractual requirements

Answer 39

C. Legal requirements

Answer 40

D. Test data.

Answer 41

A. Be easy to maintain.

Answer 42

B. Be unlikely to cause a failure.

Answer 43

C. Never fail under any circumstances.

Answer 44

D. Be written according to coding standards

Answer 45

A. Specification-based, data driven testing, and defect density techniques

Answer 46

B. Specification-based, branch coverage, and exploratory techniques

Answer 47

C. Structure-based, equivalence partitioning, and exploratory techniques

Answer 48

D. Specification-based, structure-based, and experience-based techniques

Answer 49

A. Poor quality software

Answer 50

B. Poor software and poor testing

Answer 51

C. Bad luck

Answer 52

D. Insufficient time for testing

Answer 53

A. Only records defects

Answer 54

B. Is of limited value

Answer 55

C. Is a valuable source of project information during testing if it contains all incidents

Answer 56

D. Should be used only by the test team.

Answer 57

A. The documentation is poor, so it takes longer to find out what the software is doing.

Answer 58

B. Wages are rising

Answer 59

C. The fault has been built into more documentation,code,tests, etc

Answer 60

D. None of the above

Answer 61

A. 10, 15 and 19 years

Answer 62

B. 13, 19 and 25 years

Answer 63

C. 13, 16 and 19 years

Answer 64

D. 12, 13 and 20 years

Answer 65

A. Decision table testing

Answer 66

B. State transition testing

Answer 67

C. Use case testing

Answer 68

D. Boundary value analysis

Answer 69

A. As soon as the code is written

Answer 70

B. During the design stage

Answer 71

C. When the requirements have been formally documented

Answer 72

D. As soon as possible in the development life cycle

Answer 73

A. Automation is likely to fail because of frequent changes and lack of experience

Answer 74

B. Automation is likely to fail because of GUI automation is not the right way to automate

Answer 75

C. Automation is likely to succeed because automation is very useful for frequent changes

Answer 76

D. Automation is likely to succeed because the team has been trained on tool.

Answer 77

A. A process for selecting test cases

Answer 78

B. A process for determining expected outputs

Answer 79

C. A way to measure the quality of software

Answer 80

D. A way to measure in a test plan what has to be done

Answer 81

A. To show that system will work after release

Answer 82

B. To decide when the software is of sufficient quality to release

Answer 83

C. To find as many bugs as possible before release

Answer 84

D. To give information for a risk based decision about release

Answer 85

A. Needs configuration management just like requirements, design and code

Answer 86

B. Should be newly constructed for each new version of the software

Answer 87

C. Is needed only until the software is released into production or use

Answer 88

D. Does not need to be documented and commented, as it does not form part of the released software system

Answer 89

A. IEEE829

Answer 90

B. IEEE610

Answer 91

C. BS7925-1

Answer 92

D. BS7925-2

Answer 93

A. a, b, c, d and e

Answer 94

B. a, b, c, e and f

Answer 95

C. a, c, d, e and f

Answer 96

D. a, b, c, d and f

Answer 97

A. Impact analysis

Answer 98

B. Code coverage

Answer 99

C. Gap analysts

Answer 100

D. Cyclomatic complexity

Answer 101

A. Design based

Answer 102

B. Big-bang

Answer 103

C. Bottom-up

Answer 104

D. Top-down

Answer 105

A. State analysis

Answer 106

B. Coverage analysis

Answer 107

C. Dynamic analysis

Answer 108

D. Memory analysis

Answer 109

A. Faults in program specifications are the most expensive to fix.

Answer 110

B. Faults in code are the most expensive to fix.

Answer 111

C. Faults in requirements are the most expensive to fix

Answer 112

D. Faults in designs are the most expensive to fix.

Answer 113

A. Reducing test time

Answer 114

B. No change

Answer 115

C. Increasing test time

Answer 116

D. Can't say

Answer 117

A. Statement testing

Answer 118

B. Equivalence partitioning

Answer 119

C. Error- guessing

Answer 120

D. Usability testing

Answer 121

A. As polite, constructive and helpful as possible

Answer 122

B. Firm about insisting that a bug is not a "feature" if it should be fixed

Answer 123

C. Diplomatic, sensitive to the way they may react to criticism

Answer 124

D. All of the above

Answer 125

A. Performance testing can be done during unit testing as well as during the testing of whole system

Answer 126

B. The acceptance test does not necessarily include a regression test

Answer 127

C. Verification activities should not involve testers (reviews, inspections etc)

Answer 128

D. Test environments should be as similar to production environments as possible

Answer 129

A. Component (unit) testing

Answer 130

B. Acceptance testing

Answer 131

C. System integration testing

Answer 132

D. Validation and verification

Answer 133

A. When time for testing has run out.

Answer 134

B. When all planned tests have been run

Answer 135

C. When the test completion criteria have been met

Answer 136

D. When no faults have been found by the tests run

Answer 137

A. Is nothing to do with testing

Answer 138

B. Is a partial measure of test thoroughness

Answer 139

C. Branch coverage should be mandatory for all software

Answer 140

D. Can only be applied at unit or module testing, not at system testing

Answer 141

A. State-Transition

Answer 142

B. Usability

Answer 143

C. Performance

Answer 144

D. Security

Answer 145

A. IEEE 829

Answer 146

B. IEEE 610

Answer 147

C. BS7925-1

Answer 148

D. BS7925-2

Answer 149

A. 10,11,21

Answer 150

B. 3,20,21

Answer 151

C. 3,10,22

Answer 152

D. 10,21,22

Answer 153

A. i and iii

Answer 154

B. i and ii

Answer 155

C. iii and iv

Answer 156

D. ii and iii

Answer 157

A. Code inspection

Answer 158

B. Coverage analysis

Answer 159

C. Usability assessment

Answer 160

D. Installation test

	Criado por Daniel Neag quase 7 anos atrás

Próximo

40 Questions Quiz 9 (321-360)

Descrição

Resumo de Recurso

Questão 1

Questão 2

Questão 3

Questão 4

Questão 5

Questão 6

Questão 7

Questão 8

Questão 9

Questão 10

Questão 11

Questão 12

Questão 13

Questão 14

Questão 15

Questão 16

Questão 17

Questão 18

Questão 19

Questão 20

Questão 21

Questão 22

Questão 23

Questão 24

Questão 25

Questão 26

Questão 27

Questão 28

Questão 29

Questão 30

Questão 31

Questão 32

Questão 33

Questão 34

Questão 35

Questão 36

Questão 37

Questão 38

Questão 39

Questão 40

Semelhante