As soon as the code is written
During the design stage
When the requirements have been formally documented
As soon as possible in the development life cycle
Poor quality software
Poor software and poor testing
Insufficient time for testing
To show that system will work after release
To decide when the software is of sufficient quality to release
To find as many bugs as possible before release
To give information for a risk based decision about release
Performance testing can be done during unit testing as well as during the testing of whole system
The acceptance test does not necessarily include a regression test
Verification activities should not involve testers (reviews, inspections etc)
Test environments should be as similar to production environments as possible
As polite, constructive and helpful as possible
Firm about insisting that a bug is not a “feature” if it should be fixed
Diplomatic, sensitive to the way they may react to criticism
All of the above
The most important tests first
The most difficult tests first(to allow maximum time for fixing)
The easiest tests first(to give initial confidence)
The order they are thought of
The documentation is poor, so it takes longer to find out what the software is doing.
Wages are rising
The fault has been built into more documentation,code,tests, etc
None of the above
Should be able to understand a functional specification or requirements document
Should be able to understand the source code.
Is highly motivated to find faults
Is creative to find the system’s weaknesses
A process for selecting test cases
A process for determining expected outputs
A way to measure the quality of software
A way to measure in a test plan what has to be done
Needs configuration management just like requirements, design and code
Should be newly constructed for each new version of the software
Is needed only until the software is released into production or use
Does not need to be documented and commented, as it does not form part of the released software system
Only records defects
Is of limited value
Is a valuable source of project information during testing if it contains all incidents
Should be used only by the test team.
Reducing test time
Increasing test time
Is nothing to do with testing
Is a partial measure of test thoroughness
Branch coverage should be mandatory for all software
Can only be applied at unit or module testing, not at system testing
When time for testing has run out.
When all planned tests have been run
When the test completion criteria have been met
When no faults have been found by the tests run
Component testing should be black box, system testing should be white box.
If u find a lot of bugs in testing, you should not be very confident about the quality of software
The fewer bugs you find,the better your testing was
The more tests you run, the more bugs you will find.
How well you know a particular technique
The objective of the test
How appropriate the technique is for testing the application
Whether there is a tool to support the technique
Faults in program specifications are the most expensive to fix.
Faults in code are the most expensive to fix.
Faults in requirements are the most expensive to fix
Faults in designs are the most expensive to fix.