DELIVERABLES
It
is the output from the testing team. It contains what we will deliver to the
customer at the end of the project. It has the following sections,
1. Test Plan
2. Test Cases
3. Test Scripts
4. Traceability Matrix
5. Defect Report
6. Test Execution Report
7. Graphs and Metrics
8. Release Note
Graphs and Metrics
Here,
we will just mention what are the types of graphs we will deliver and also give
a sample of each graph we will be delivering.
 |
 |
|
Graph
1 :- in this graph we depict – how many bugs have been found and how many bugs
have been fixed in each module.
Graph
2 :- in this graph, we depict – how many critical, major and minor bugs have
been found for each module and how many have been fixed for each module.
Graph
3 :- in this graph, we depict – build wise graph i.e, in each build how many
bugs have been found and fixed for each module. According to the module, we
have found defects. Adding C has introduced a lot of bugs in A and B. Adding D
has introduced a lot of bugs in A, B and C.
Graph
4 :- Defect Trend Analysis graph depicts – this graph is prepared every month
and we must send it to management. It’s a kind of forecast. By the end of the
project, “rate of fixing defects” curve must have an upward trend. Test Lead
prepares this graph.
Graph
5 :- Test manager prepares this graph. This graph is prepared to understand the
gap in estimation of defects and the actual defects that have occurred. This
graph helps in better estimation of defects in the future.
Metrics
We
generate the defect distribution graph(graph 1) by looking at the above data.
Similarly
we can generate many such metrics.
For
example,
 |
In
the above graph, we are maintain a record of all the test engineers in the
project and how many bugs have been caught and fixed etc. We can use this data
for future analysis. When a new requirement comes, we can decide who to give
the complex feature for testing based on the number of bugs they have found. We
will be in a better position to know who can handle the complex features very
well and find maximum number of bugs.
Release Note:
The
release note contains,
1)
List of pending/open bugs
…
…
2)
List of features added, modified or deleted
…
…
3)Platforms(OS,
Browsers, Hardware) in which the product is tested
..
..
4)
Platforms in which the product is not tested
…
…
5)List
of bugs fixed in current release which were found in previous release
production
..
…
Let us consider that
Diamond release is the 2nd release of the product after the 1st
release Perl release. Some of the bugs found in the 1st release has
been fixed in the 2nd release. Also a list of features which have
been added, modified and deleted from the 1st release to the 2nd
release will be mentioned here.
6) Procedure to
install the software
...
…
7) Version of the
software
..
Release Note is a document prepared during release of
the project and signed by test manager
