40 Question quiz 6 (201-240)

Question

The inputs for developing a test plan are taken from

Answer 1

A. Project plan

Answer 2

B. Business plan

Answer 3

C. Support plan

Answer 4

D. None of the above

Answer 5

A. A dynamic analysis tool

Answer 6

B. A test execution tool

Answer 7

C. A debugging tool

Answer 8

D. A test management tool

Answer 9

E. A configuration management tool

Answer 10

A. Error guessing

Answer 11

B. Walkthrough

Answer 12

C. Data flow analysis

Answer 13

D. Inspections

Answer 14

A. Test procedure specification

Answer 15

B. Test design specification

Answer 16

C. Test case specification

Answer 17

D. Test plan

Answer 18

A. Variables not defined in the code

Answer 19

B. Spelling and grammar faults in the documents

Answer 20

C. Requirements that have been omitted from the design documents

Answer 21

D. How much of the code has been covered

Answer 22

A. Operability

Answer 23

B. Observability

Answer 24

C. Simplicity

Answer 25

D. Robustness

Answer 26

A. Coverage management tool

Answer 27

B. Test management tool

Answer 28

C. Data preparation tool

Answer 29

D. Performance testing tool

Answer 30

A. We cannot run the test

Answer 31

B. It may be difficult to repeat the test

Answer 32

C. It may be difficult to determine if the test has passed or failed

Answer 33

D. We cannot automate the user inputs

Answer 34

A. This question is difficult to answer

Answer 35

B. The answer depends on the contract with the client, special requirements if any & risks your organization is willing to take

Answer 36

C. The answer depends on the experience & maturity of your developers

Answer 37

D. The answer should be standardized for the software development industry

Answer 38

A. To freeze requirements

Answer 39

B. To understand user needs

Answer 40

C. To define the scope of testing

Answer 41

D. All of the above

Answer 42

A. Simple Loops

Answer 43

B. Nested Loops

Answer 44

C. Concatenated Loops

Answer 45

D. All of the above

Answer 46

A. White box

Answer 47

B. Black box

Answer 48

C. Green box

Answer 49

D. Yellow box

Answer 50

A. Is unlikely to be completed on schedule

Answer 51

B. Is unlikely to cause a failure

Answer 52

C. Is likely to be fault-free

Answer 53

D. Is likely to be liked by the users

Answer 54

A. Being diplomatic

Answer 55

B. Able to write software

Answer 56

C. Having good attention to detail

Answer 57

D. Able to be relied on

Answer 58

A. Will always be automated

Answer 59

B. Will help ensure unchanged areas of the software have not been affected

Answer 60

C. Will help ensure changed areas of the software have not been affected

Answer 61

D. Can only be run during user acceptance testing

Answer 62

A. Interim Test report

Answer 63

B. Final test report

Answer 64

C. Project status report

Answer 65

D. Management report

Answer 66

A. Top-down integration

Answer 67

B. Bottom-up integration

Answer 68

C. None of the above

Answer 69

D. Module integration

Answer 70

A. Checking that we are building the right system

Answer 71

B. Checking that we are building the system right

Answer 72

C. Performed by an independent test team

Answer 73

D. Making sure that it is what the user really wants

Answer 74

A. Re-testing is running a test again; regression testing looks for unexpected side effects

Answer 75

B. Re-testing looks for unexpected side effects; regression testing is repeating those tests

Answer 76

C. Re-testing is done after faults are fixed; regression testing is done earlier

Answer 77

D. Re-testing uses different environments, regression testing uses the same environment

Answer 78

E. Re-testing is done by developers, regression testing is done by independent testers

Answer 79

A. All the planned tests have been run

Answer 80

B. Time has run out

Answer 81

C. All faults have been fixed correctly

Answer 82

D. Both A. and C.

Answer 83

E. I depends on the risks for the system being tested

Answer 84

A. White-box technique

Answer 85

B. Component testing

Answer 86

C. Black-box technique

Answer 87

D. Data driven testing

Answer 88

A. Status accounting of configuration items

Answer 89

B. Auditing conformance to ISO9001

Answer 90

C. Identification of test versions

Answer 91

D. Record of changes to documentation over time

Answer 92

E. controlled library access

Answer 93

A. What is selected for testing

Answer 94

B. Objectives and results

Answer 95

C. Expected results

Answer 96

D. Targets and misses

Answer 97

A. A dynamic analysis tool

Answer 98

B. A test execution tool

Answer 99

C. A debugging tool

Answer 100

D. A test management tool

Answer 101

E. A configuration management tool

Answer 102

A. Is not important

Answer 103

B. Increases as we move the product towards live use

Answer 104

C. Decreases as we move the product towards live use

Answer 105

D. Is more expensive if found in requirements than functional design

Answer 106

E. Can never be determined

Answer 107

A. 1000, 5000, 99999

Answer 108

B. 9999, 50000, 100000

Answer 109

C. 10000, 50000, 99999

Answer 110

D. 10000, 99999

Answer 111

E. 9999, 10000, 50000, 99999, 10000

Answer 112

A. An error

Answer 113

B. A fault

Answer 114

C. A failure

Answer 115

D. A defect

Answer 116

E. A mistake

Answer 117

A. Component interaction

Answer 118

B. Probe effect

Answer 119

C. State transition

Answer 120

D. Disaster recovery

Answer 121

A. 1 test for statement coverage, 1 for branch coverage

Answer 122

B. 1 test for statement coverage, 2 for branch coverage

Answer 123

C. 1 test for statement coverage. 3 for branch coverage

Answer 124

D. 2 tests for statement coverage, 2 for branch coverage

Answer 125

E. 2 tests for statement coverage, 3 for branch coverage

Answer 126

A. Report on deviations from the project plan

Answer 127

B. Sign the system off for release

Answer 128

C. Re-allocate resource to meet original plans

Answer 129

D. Rise incidents on faults that they have found

Answer 130

E. Provide information for risk analysis and quality improvement

Answer 131

A. Business process-based testing

Answer 132

B. Performance, load and stress testing

Answer 133

C. Requirements-based testing

Answer 134

D. Usability testing

Answer 135

E. Top-down integration testing

Answer 136

A. A small team to establish the best way to use the tool

Answer 137

B. Everyone who may eventually have some use for the tool

Answer 138

C. The independent testing team

Answer 139

D. The managers to see what projects it should be used in

Answer 140

E. The vendor contractor to write the initial scripts

Answer 141

A. Measuring response time

Answer 142

B. Measuring transaction rates

Answer 143

C. Recovery testing

Answer 144

D. Simulating many users

Answer 145

E. Generating many transactions

Answer 146

A. To know when a specific test has finished its execution

Answer 147

B. To ensure that the test case specification is complete

Answer 148

C. To set the criteria used in generating test inputs

Answer 149

D. To know when test planning is complete

Answer 150

E. To plan when to stop testing

Answer 151

A. 1 test for statement coverage, 3 for branch coverage

Answer 152

B. 2 tests for statement coverage, 2 for branch coverage

Answer 153

C. 2 tests for statement coverage. 3 for branch coverage

Answer 154

D. 3 tests for statement coverage, 3 for branch coverage

Answer 155

E. 3 tests for statement coverage, 2 for branch coverage

Answer 156

A. Code reviews

Answer 157

B. Code inspections

Answer 158

C. A coverage tool

Answer 159

D. A test management tool

Answer 160

E. A static analysis tool

Answer 161

A. How to fix the fault

Answer 162

B. How to reproduce the fault

Answer 163

C. Test environment details

Answer 164

D. Severity, priority

Answer 165

E. The actual and expected outcomes

Answer 166

A. Test items (i.e. software versions)

Answer 167

B. What is not to be tested

Answer 168

C. Test environments

Answer 169

D. Quality plans

Answer 170

E. Schedules and deadlines

Answer 171

A. Test items

Answer 172

B. Test deliverables

Answer 173

C. Test tasks

Answer 174

D. Test environment

Answer 175

E. Test specification

	Erstellt von Daniel Neag vor mehr als 6 Jahre

Nächster

40 Question quiz 6 (201-240)

Beschreibung

Zusammenfassung der Ressource

Frage 1

Frage 2

Frage 3

Frage 4

Frage 5

Frage 6

Frage 7

Frage 8

Frage 9

Frage 10

Frage 11

Frage 12

Frage 13

Frage 14

Frage 15

Frage 16

Frage 17

Frage 18

Frage 19

Frage 20

Frage 21

Frage 22

Frage 23

Frage 24

Frage 25

Frage 26

Frage 27

Frage 28

Frage 29

Frage 30

Frage 31

Frage 32

Frage 33

Frage 34

Frage 35

Frage 36

Frage 37

Frage 38

Frage 39

Frage 40

ähnlicher Inhalt