6. Test Management

Descripción

qa
Rachel Sprague
Test por Rachel Sprague, actualizado hace más de 1 año
Rachel Sprague
Creado por Rachel Sprague hace más de 8 años
178
0

Resumen del Recurso

Pregunta 1

Pregunta
Which is a benefit of independence in testing?
Respuesta
  • It frees up valuable development time
  • The tests are unbiased
  • Developers do not need to learn how to design tests
  • It reduces the need for communication between testers and developers

Pregunta 2

Pregunta
Which is a potential drawback of independent testing?
Respuesta
  • Over reliance on the independent test team
  • Developers get less opportunity to gain testing experience
  • Testers lose the chance to socialise with developers
  • Developers may lose a sense of responsibility for quality

Pregunta 3

Pregunta
Test leader tasks include:
Respuesta
  • Creating test specifications
  • Planning the tests
  • Prepare and acquire test data
  • Setting up the test environment

Pregunta 4

Pregunta
The Test Leader role may be performed by:
Respuesta
  • A Quality Manager
  • Any manager
  • Any tester
  • A Business Unit manager

Pregunta 5

Pregunta
Typical tester tasks include:
Respuesta
  • Reviewing test policy
  • Monitoring test results and checking exit criteria
  • Introducing suitable metrics for progress monitoring
  • Reviewing tests written by others

Pregunta 6

Pregunta
Which of the following is a possible approach to independent testing?
Respuesta
  • Project planning done independently from test planning
  • Ensuring that each test level is tested separately
  • The use of specialists for specific test types (e.g. certification testers
  • The test management role is isolated from the project management role

Pregunta 7

Pregunta
Which of the following is not a test planning task?
Respuesta
  • Defining the test documentation
  • Assessing the meeting of exit criteria
  • Assigning resources for the different activities defined
  • Selecting metrics for monitoring progress

Pregunta 8

Pregunta
Which of the following is a test planning task?
Respuesta
  • Defining the overall test approach
  • Preparing test specifications
  • Evaluating exit criteria and reporting
  • Reviewing actual results against expected results

Pregunta 9

Pregunta
Which of the following would you find listed in the IEEE standard 829 Test Plan Outline?
Respuesta
  • Features not to be tested
  • Test specifications
  • Test conditions
  • Documentation standards for test procedures

Pregunta 10

Pregunta
The IEEE829 test plan outline applies to:
Respuesta
  • The master test plan and test level plans equally
  • Test level plans only
  • The master test plan only
  • The test schedule

Pregunta 11

Pregunta
Test planning is influenced by:
Respuesta
  • Known constraints
  • The number of failures encountered
  • The test schedule
  • The size of the development team

Pregunta 12

Pregunta
What is the purpose of test exit criteria?
Respuesta
  • To know when a specific test has finished its execution
  • To ensure that the test case specification is complete
  • To identify when testers should stop working
  • To define when to stop testing

Pregunta 13

Pregunta
The following are examples of typical entry criteria except:
Respuesta
  • Test environment readiness
  • Estimates of expected testing duration being available
  • Test data available
  • Tool readiness in the test environment

Pregunta 14

Pregunta
Which of the following is not an example of exit criteria?
Respuesta
  • Cost
  • Code coverage measures
  • The number of defects found
  • Estimates of defect density

Pregunta 15

Pregunta
Exit criteria may be defined in terms of:
Respuesta
  • Lines of source code
  • The number of testers available
  • Lack of coverage in certain areas and defects not fixed
  • Test environment availability

Pregunta 16

Pregunta
Which of the following concerning test estimating is untrue?
Respuesta
  • Estimates can be based on metrics of former or similar projects
  • Estimates can be based on estimates made by the owner of the tasks or by experts
  • Total testing effort depends on the outcome of testing
  • Estimating is pointless as estimates are never correct

Pregunta 17

Pregunta
One purpose of test progress monitoring is to:-
Respuesta
  • Enable initial estimates of test effort to be made more accurately
  • Give visibility to the test activities
  • Evaluate tester ability for appraisal purposes
  • Determine metric requirements

Pregunta 18

Pregunta
Common test progress metrics include:
Respuesta
  • Initial estimates of test effort
  • Holiday days taken by testers
  • Percentage of work done in test case preparation
  • Developer hours to date

Pregunta 19

Pregunta
The outline of a test summary report is given in:
Respuesta
  • BS 7925-2
  • IEEE 829
  • ISO 9000
  • BS 7925-1

Pregunta 20

Pregunta
Metrics should be collected during and at the end of a test level in order to assess:
Respuesta
  • The performance of the development team
  • The quality of the test documentation
  • The effectiveness of the testers
  • The outstanding risk

Pregunta 21

Pregunta
Which of the following is not true of test control?
Respuesta
  • It collects metrics for monitoring purposes
  • It can set entry criterion requiring fixes to have been retested by a developer before accepting them into a build
  • Corrective actions taken may cover any test activity
  • Corrective actions taken may affect any other software life cycle activity

Pregunta 22

Pregunta
Which is not a function of configuration management?
Respuesta
  • Tracking changes to testware
  • Version control of testware
  • Defining the format for test deliverables
  • Identifying items of testware

Pregunta 23

Pregunta
What is the difference between a project risk and a product risk?
Respuesta
  • Project risks are used to prioritise tests and to determine the extent of testing; product risks are a development concern not a testing concern
  • 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
  • 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
  • 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

Pregunta 24

Pregunta
Which of the following is determined by the level of product risk identified?
Respuesta
  • Test priorities and the extent of testing
  • The need for and amount of test automation
  • The need for accurate incident reporting
  • The contents of the regression test pack

Pregunta 25

Pregunta
Which one of the following should be given in an incident report?
Respuesta
  • Suggestions on how to fix it
  • Identification of the test that failed
  • The developer who wrote the defective code
  • The cause of the incident

Pregunta 26

Pregunta
Which is an objective of incident reporting?
Respuesta
  • To provide ideas for test process improvement
  • To provide ideas for developer improvement
  • To provide ideas on how to fix the problem
  • To measure individual tester defect discovery rates
Mostrar resumen completo Ocultar resumen completo

Similar

How well do you know GoConqr?
Sarah Egan
2. Testing Through LIfecycle
Rachel Sprague
3-4. Test Design
Rachel Sprague
7. Tool Support for Testing
Rachel Sprague
5. Static Techniques
Rachel Sprague
dimension tests
dario.budimir
1. Fundamentals
Rachel Sprague
Test
jeanber