Review process itself
Testing whether a known software fault been fixed.
Executing a large number of different tests.
Testing whether modifications have introduced adverse side effects.
Using a test automation tool.
Dynamic analysis tool
Static Analysis tool.
Number of independent paths in the basis set of a program
Number of binary decisions + 1
Number bound for the number of tests that must be conducted to ensure that all statements have been executed at least once
Number of branches and decisions
Features to be tested.
1-b, 2-c, 3-a
1-b, 2-a, 3-c
1-c, 2-a, 3-b
1-a, 2-b, 3-c
When the specified number of faults are found.
When the test completion criteria are met.
When all high and medium priority tests are complete.
When all statements have been executed
1-d, 2-c, 3-d, 4-a.
1-d, 2-a, 3-c, 4-b.
1-a, 2-b, 3-d, 4-c.
1-c, 2-b, 3-a, 4-d.
Testing the system when combined with other systems.
Testing a sub-system using stubs and drivers.
Testing a system with a large number of users.
Combing software components and testing them in one go.
Data Flow testing.
1&2 are true and 3 is false.
1,2&3 are true.
1 is true, 2&3 are false.
1&2 are false, 3 is true
Incidents should always be investigated and resolved.
Incidents occur when expected and actual results differ.
Incidents can be analyzed to assist in test process improvement.
An incident can be raised against documentation.
Check user friendliness.
Improve software accuracy
This is an acceptable risk of a multi-user system.
Insufficient functional testing has been performed.
This indicates an important non-functional requirement was not specified and tested.
It is not possible to test against such events prior to release.
Deviation from expected result to actual result
Defect in the software.
Error in the program code.
Fault in the system.
Ensure the test item is adequately tested.
Make the need for black-box testing redundant.
Run the risk that the requirements are not satisfied.
Suffices for the unit testing phase.
Estimating test duration.
Use of automated test execution tools.
Testing performed by users.
Testing against acceptance test criteria.
Integration of system with user documentation.
It is easy to execute.
It is designed to detect faults if present.
The expected outcome is specified before execution.
It is unlikely to delay progress.
An appropriate way of deriving system tests.
Only used if good requirements are not available.
Only used when good requirements are available.
The most appropriate way of deriving system tests.
Be easy to maintain.
Be unlikely to cause a failure.
Never fail under any circumstances.
Be written according to coding standards
Poor quality software
Poor software and poor testing
Insufficient time for testing
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.
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
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.
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
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