Which is a benefit of independence in testing?
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
Which is a potential drawback of independent testing?
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
Test leader tasks include:
Creating test specifications
Planning the tests
Prepare and acquire test data
Setting up the test environment
The Test Leader role may be performed by:
A Quality Manager
Any manager
Any tester
A Business Unit manager
Typical tester tasks include:
Reviewing test policy
Monitoring test results and checking exit criteria
Introducing suitable metrics for progress monitoring
Reviewing tests written by others
Which of the following is a possible approach to independent testing?
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
Which of the following is not a test planning task?
Defining the test documentation
Assessing the meeting of exit criteria
Assigning resources for the different activities defined
Selecting metrics for monitoring progress
Which of the following is a test planning task?
Defining the overall test approach
Preparing test specifications
Evaluating exit criteria and reporting
Reviewing actual results against expected results
Which of the following would you find listed in the IEEE standard 829 Test Plan Outline?
Features not to be tested
Test specifications
Test conditions
Documentation standards for test procedures
The IEEE829 test plan outline applies to:
The master test plan and test level plans equally
Test level plans only
The master test plan only
The test schedule
Test planning is influenced by:
Known constraints
The number of failures encountered
The size of the development team
What is the purpose of test exit criteria?
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
The following are examples of typical entry criteria except:
Test environment readiness
Estimates of expected testing duration being available
Test data available
Tool readiness in the test environment
Which of the following is not an example of exit criteria?
Cost
Code coverage measures
The number of defects found
Estimates of defect density
Exit criteria may be defined in terms of:
Lines of source code
The number of testers available
Lack of coverage in certain areas and defects not fixed
Test environment availability
Which of the following concerning test estimating is untrue?
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
One purpose of test progress monitoring is to:-
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
Common test progress metrics include:
Initial estimates of test effort
Holiday days taken by testers
Percentage of work done in test case preparation
Developer hours to date
The outline of a test summary report is given in:
BS 7925-2
IEEE 829
ISO 9000
BS 7925-1
Metrics should be collected during and at the end of a test level in order to assess:
The performance of the development team
The quality of the test documentation
The effectiveness of the testers
The outstanding risk
Which of the following is not true of test control?
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
Which is not a function of configuration management?
Tracking changes to testware
Version control of testware
Defining the format for test deliverables
Identifying items of testware
What is the difference between a project risk and a product risk?
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
Which of the following is determined by the level of product risk identified?
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
Which one of the following should be given in an incident report?
Suggestions on how to fix it
Identification of the test that failed
The developer who wrote the defective code
The cause of the incident
Which is an objective of incident reporting?
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
