6. Test Management

Question

Which is a benefit of independence in testing?

Answer 1

It frees up valuable development time

Answer 2

The tests are unbiased

Answer 3

Developers do not need to learn how to design tests

Answer 4

It reduces the need for communication between testers and developers

Answer 5

Over reliance on the independent test team

Answer 6

Developers get less opportunity to gain testing experience

Answer 7

Testers lose the chance to socialise with developers

Answer 8

Developers may lose a sense of responsibility for quality

Answer 9

Creating test specifications

Answer 10

Planning the tests

Answer 11

Prepare and acquire test data

Answer 12

Setting up the test environment

Answer 13

A Quality Manager

Answer 14

Any manager

Answer 15

Any tester

Answer 16

A Business Unit manager

Answer 17

Reviewing test policy

Answer 18

Monitoring test results and checking exit criteria

Answer 19

Introducing suitable metrics for progress monitoring

Answer 20

Reviewing tests written by others

Answer 21

Project planning done independently from test planning

Answer 22

Ensuring that each test level is tested separately

Answer 23

The use of specialists for specific test types (e.g. certification testers

Answer 24

The test management role is isolated from the project management role

Answer 25

Defining the test documentation

Answer 26

Assessing the meeting of exit criteria

Answer 27

Assigning resources for the different activities defined

Answer 28

Selecting metrics for monitoring progress

Answer 29

Defining the overall test approach

Answer 30

Preparing test specifications

Answer 31

Evaluating exit criteria and reporting

Answer 32

Reviewing actual results against expected results

Answer 33

Features not to be tested

Answer 34

Test specifications

Answer 35

Test conditions

Answer 36

Documentation standards for test procedures

Answer 37

The master test plan and test level plans equally

Answer 38

Test level plans only

Answer 39

The master test plan only

Answer 40

The test schedule

Answer 41

Known constraints

Answer 42

The number of failures encountered

Answer 43

The test schedule

Answer 44

The size of the development team

Answer 45

To know when a specific test has finished its execution

Answer 46

To ensure that the test case specification is complete

Answer 47

To identify when testers should stop working

Answer 48

To define when to stop testing

Answer 49

Test environment readiness

Answer 50

Estimates of expected testing duration being available

Answer 51

Test data available

Answer 52

Tool readiness in the test environment

Answer 53

Code coverage measures

Answer 54

The number of defects found

Answer 55

Estimates of defect density

Answer 56

Lines of source code

Answer 57

The number of testers available

Answer 58

Lack of coverage in certain areas and defects not fixed

Answer 59

Test environment availability

Answer 60

Estimates can be based on metrics of former or similar projects

Answer 61

Estimates can be based on estimates made by the owner of the tasks or by experts

Answer 62

Total testing effort depends on the outcome of testing

Answer 63

Estimating is pointless as estimates are never correct

Answer 64

Enable initial estimates of test effort to be made more accurately

Answer 65

Give visibility to the test activities

Answer 66

Evaluate tester ability for appraisal purposes

Answer 67

Determine metric requirements

Answer 68

Initial estimates of test effort

Answer 69

Holiday days taken by testers

Answer 70

Percentage of work done in test case preparation

Answer 71

Developer hours to date

Answer 72

The performance of the development team

Answer 73

The quality of the test documentation

Answer 74

The effectiveness of the testers

Answer 75

The outstanding risk

Answer 76

It collects metrics for monitoring purposes

Answer 77

It can set entry criterion requiring fixes to have been retested by a developer before accepting them into a build

Answer 78

Corrective actions taken may cover any test activity

Answer 79

Corrective actions taken may affect any other software life cycle activity

Answer 80

Tracking changes to testware

Answer 81

Version control of testware

Answer 82

Defining the format for test deliverables

Answer 83

Identifying items of testware

Answer 84

Project risks are used to prioritise tests and to determine the extent of testing; product risks are a development concern not a testing concern

Answer 85

Project risks are potential failure areas in the software or system; product risks are risks that surround the project’s capability to deliver its objectives

Answer 86

Project risks are the risks that surround the project’s capability to deliver its objectives; product risks are potential failure areas in the software or system

Answer 87

Product risks are typically related to supplier issues, organizational factors and technical issues; Project risks are concerned with poor software characteristics, potential to cause harm, and poor data integrity

Answer 88

Test priorities and the extent of testing

Answer 89

The need for and amount of test automation

Answer 90

The need for accurate incident reporting

Answer 91

The contents of the regression test pack

Answer 92

Suggestions on how to fix it

Answer 93

Identification of the test that failed

Answer 94

The developer who wrote the defective code

Answer 95

The cause of the incident

Answer 96

To provide ideas for test process improvement

Answer 97

To provide ideas for developer improvement

Answer 98

To provide ideas on how to fix the problem

Answer 99

To measure individual tester defect discovery rates

Próximo

6. Test Management

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

Semelhante

	Criado por Rachel Sprague mais de 8 anos atrás