Pr e-meeting preparations
Formal follow-up process
Scenario, Dry group, Peer group
SC = 2 ; CC = 5
SC = 4 ; CC = 5;
SC = 3 ; CC = 3
SC = 2 ; CC = 2
A, b , d are correct ; c is incorrect
D, c is correct ; a, b are incorrect.
B is correct ; a, c, d are incorrect .
B, c are correct ; a, d are incorrect
The more tests you run , the more bugs you will find.
The fewer the bugs, the better the testing you have done.
Component testing is a black-box testing , and system testing is white-box testing.
If you find a lot of bugs while testing, then, you should not be quite confident about the software product.
One or more test design specification documents.
A test type.
A testing technique.
A group of test activities that are organized together.
Tests are derived based on the tester's skills and experience.
Tests are derived from models that specify the problem to be solved by the software or its components.
Tests are derived from the extent of the coverage of structural elements of the system/components.
Tests are derived from information about how the software is constructed.
Statement coverage Tool
Static Analysis Tool
Test Management Tool
Decision coverage Tool
BS 7925 -1
BS 7925 - 2
Scheduling test implementation
Determining the scope.
Implementing the test policy.
Initiating the corrective actions.
Metrics management tools
Progress tracking tools
Test execution tools
Test management tools
Planning ; kick-off ; Review meeting ; defects logging ; Rework ; Follow-up
Planning ; select personnel ; define entry and exit criteria ; log defects; fix defects; follow-up
Planning ; Kick-off ; individual preparation ; review meeting ; rework ; follow-up
Planning ; kick-off ; individual preparation; fix defects ; rework ; exit phase
12, 13, 15, 19, 20, 21
11, 12, 13 , 19, 20, 21
12, 13, 14, 18, 19, 20
10, 11, 12, 17, 18, 19
A reviewed test plan
Availability of tools to support the review process.
Trained participants and leaders.
A separate recorder during the review meeting.
A chronological record of relevant details about the execution of tests.
A document describing the scope, approach , resources and schedule of intended test activities.
Artifacts produced during the test process required to plan ,design and execute tests , such as documentation, scripts, inputs, expected results , and any additional software or utilities used in testing
A set of several test cases for a component/system under test, where the postcondition of one test is often used as precondition for the next one.
Measuring response time on an on-line ticket booking system.
Checking how easy the system is to use.
Checking the on-line booking screen information and the database contents against the information on the letter to the customers.
Checking the effort of high volumes of traffic in a call-center system.
Test implementation and execution
Test analysis and design
Test planning and control
Evaluating test exit criteria
You have completed every test in the test plan.
You have detected every bug in the software .
You have reached the schedule ship date .
You have tested every statement, branch and combination of branches in the program.
A process of selecting test cases.
A way to measure the quality of the software.
A process of determining expected outputs.
A way to measure in a test plan what has to be done.
C and d
A and c
B and c
B and d
Requirement specification, website, code , use cases
Requirement specification , user guide, performance
Requirement specification , test cases , user guide
Requirement specification , test plan, test memory leaks