Testing Documentation

1.

Testing
Documentation

2.

Types of Testing Documentation
• Test Plan
• Test Cases
• Checklists
• Test Reports
• Bug Reports

3.

Test Plan
A document detailing the objectives, resources, and processes for a specific test for a software or
hardware product. The plan typically contains a detailed understanding of the eventual workflow.
A document describing the scope, approach, resources and schedule of intended test activities.

4.

Test Plan variants
• Project Test Plan
• Release Test Plan
(Feature Test Plan)

5.

Key Points of Test Plan
• Scope of testing
• Budget
• Timeline
• Resources

6.

Structure of Test Case
• Test Case ID (unique)*
• Title*
• Pre-condition/Prerequisites
• User roles
• Steps*
• Test data
• Expected result*
• Status*
• Comment
TC1
‘Create an
order’
button
activation
1.
2.
Navigate to
www.online
bookstore.o
rg
Log in with
valid
credentials
Any
1.
2.
3.
4.
5.
Navigate to the
Catalogue tab
Scroll to C section
Click ‘Christmas Carol’
book
Click Add to Chart
Navigate to the Chart
Tab
1.
2.
3.
4.
5.
Catalogue with books is
displayed
C section with books starting
with C are displayed in
alphabetical order
Christmas Carol book preview is
displayed with Back button
‘A book is added to a chart.’
message is displayed.
‘Create an order’ button is
active on a Chart Tab.
Untested

7.

Checklist
It is a high-level list of items to be noted, checked, or remembered, or a set
of rules or criteria against which a product must be verified.

8.

Structure of Checklist
• ID*
• Description*
• Status*
• Comment
CL1
Verify the UI elements on Catalogue tab
(color, borders, controls size etc.)
passed
CL2
Delete recently added item from the Chart
failed
‘Delete’ button is missing.
[link to a bug]

9.

Test Case vs Checklist
• How to be tested
• What to be tested
• Detailed
• One liner statement
• Set of steps
• Thread of operations
• Guardlines for newcomers
• Need background knowledge
• Time-consuming
• Time-saving

10.

Test Reports
Test status report – A testing status report is a report that contains a summary of all
the testing-related activities that happened within a particular time. It highlights the
status of the project using quantitative information. This makes it an effective
communication tool between project teams and key stakeholders, which may include
QA managers, product managers, release managers, and other folks on the leadership
team.
Test progress report - A document summarizing testing activities and results,
produced at regular intervals, to report progress of testing activities against a baseline
(such as the original test plan) and to communicate risks and alternatives requiring a
decision to management.
Test summary report - A document summarizing testing activities and results. It also
contains an evaluation of the corresponding test items against exit criteria.

11.

Test status report (Daily)

12.

13.

Defect Report
It is a document reporting on any flaw in a component or system that can
cause the component or
system to fail to perform its required function.

14.

Structure of Defect Report
• ID*
• Summary*
• Steps to reproduce*
• Actual result*
• Expected result*
• Component
• Severity
• Priority*
• Attachments
• Environment
• Label
• Requirement link etc.