Makes test preparation easier.
Means inspections are not required.
Can prevent fault multiplication.
Will find all faults.
Linkage of customer requirements to version numbers.
Facilities to compare test results with expected results.
The precise differences in versions of software component source code.
Restricted access to the source code library.
Tests the individual components that have been developed.
Tests interactions between modules or subsystems.
Only uses components that form part of the live system.
Tests interfaces to other systems.
The system shall be user friendly.
The safety-critical parts of the system s all contain 0 faults.
The response time shall be less than one second for the specified design load.
The system shall be built to be portable.
Enable the code to be tested before the execution environment is ready.
Can be performed by the person who wrote the code.
Can be performed by inexperienced staff.
Are cheap to perform.
Test recording.
Test planning.
Test configuration.
Test specification.
Found in the software; the result of an error.
Departure from specified behaviour.
An incorrect step, process or data definition in a computer program.
A human action that produces an incorrect result.
Metrics from previous similar projects
Discussions with the development team
Time allocated for regression testing
A. & B.
V-3,w-2,x-1,y-5,z-4
V-2,w-5,x-1,y-4,z-3
V-3,w-4,x-1,y-5,z-2
V-2,w-1,x-4,y-3,z-5
£1500
£32001
£33501
£28000
Test coverage criteria can be measured in terms of items exercised by a test suite.
A measure of test coverage criteria is the percentage of user requirements covered.
A measure of test coverage criteria is the percentage of faults found.
Test coverage criteria are often used when specifying test completion criteria.
3
4
5
6
To find faults in the software.
To assess whether the software is ready for release.
To demonstrate that the software doesn’t work.
To prove that the software is correct.
Time runs out.
The required level of confidence has been achieved.
No more faults are found.
The users won’t find any serious faults.
Actual results
Program specification
User requirements
System specification
I, iii, iv, v.
Ii, iv and v.
I, ii and iv.
I and v.
All document reviews involve the development team.
Some, but not all, development activities have corresponding test activities.
Each test level has test objectives specific to that level.
Analysis and design of tests begins as soon as development is complete.
Iii, i, iv, ii.
Iii, iv, i, ii.
Iii, ii, i, iv.
Ii, iii, i, iv.
An independent tester may find defects more quickly than the person who wrote the software.
An independent tester may be more focused on showing how the software works than the person who wrote the software.
An independent tester may be more effective and efficient because they are less familiar with the software than the person who wrote it.
An independent tester may be more effective at finding defects missed by the person who wrote the software.
17, 18, 19.
29, 30, 31.
18, 29, 30.
17, 29, 31.
Ii is True; i, iii, iv & v are False
I & v are True; ii, iii & iv are False
Ii & iii are True; i, iv & v are False
Ii, iii & iv are True; i & v are False
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.
Project risks are typically related to supplier issues, organizational factors and technical issues; product risks are typically related to skill and staff shortages.
Project risks are risks that delivered software will not work; product risks are typically related to supplier issues, organizational factors and technical issues.
Test implementation and execution.
Evaluating test exit criteria.
Test analysis and design.
Test planning and control.
To communicate how incidents will be managed.
To communicate how testing will be performed.
To produce a test schedule.
To produce a work breakdown structure.
Test plan.
Test procedure specification.
Test case specification.
Test design specification.
Determining the test approach.
Preparing test specifications.
Evaluating exit criteria and reporting.
Measuring and analyzing results.
To determine the programming effort needed to make the changes.
To determine the programming effort needed to make the changes.
To determine how much the planned changes will affect users.
To determine how the existing system may be affected by changes.
£28000.
£33501.
£32001.
£1500.
Dynamic Analysis tool.
Test Execution tool.
Static Analysis tool.
Security tool.
Exercise system functions in proportion to the frequency they will be used in the released product
Push the system beyond its designed operation limits and are likely to make the system fail
Exercise unusual and obscure scenarios that may not have been considered in design
Exercise the most complicated and the most error-prone portions of the system
Quiz Review Timeline +
Our quizzes are rigorously reviewed, monitored and continuously updated by our expert board to maintain accuracy, relevance, and timeliness.
Wait!
Here's an interesting quiz for you.