Scribd
Upload
270 views

Testing Documentation

Testing documentation outlines the strategy, resources, and schedule for testing an application. It includes test plans, test cases, and traceability matrices. A test plan describes the common testing approach, assumptions, test cases, features to be tested, and resources. A test case is a set of inputs, steps, and conditions used to test software functionality and find errors. It typically includes an ID, product details, purpose, pre-conditions, steps, expected outcomes, and post-conditions. Documentation is important for evaluating testing needs, requirements tracking, and test coverage.

Uploaded by

Vinayak
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
270 views

Testing Documentation

Testing documentation outlines the strategy, resources, and schedule for testing an application. It includes test plans, test cases, and traceability matrices. A test plan describes the common testing approach, assumptions, test cases, features to be tested, and resources. A test case is a set of inputs, steps, and conditions used to test software functionality and find errors. It typically includes an ID, product details, purpose, pre-conditions, steps, expected outcomes, and post-conditions. Documentation is important for evaluating testing needs, requirements tracking, and test coverage.

Uploaded by

Vinayak
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Testing Documentation

Documentation as part of process

Testing documentation is usually associated with the documentation of artifacts that should be
developed before or during the testing of software.

Testing Documentation is an important part of the testing process.


Documentation for software testing is necessary for evaluating the testing effort needed, requirement
tracking/tracing, test coverage etc.

Further are described commonly used documented artifacts concerning software testing:

 Test Plan.
 Test Case.
 Test Scenario.
 Traceability Matrix.

Test Plan

A Test plan outlines the common strategy that will be applied to test an application, the resources
that will be used, the test environment in which testing will be performed, and the schedule of testing
activities along with the limitations. Typically writing a Test Plan is the competence of the Quality
Assurance Team Lead.

Test plan outlines the common strategy that will be applied to test an
application.
A test plan includes the following:

 Introduction to the Test Plan document.


 Assumptions while testing the application.
 Approaches to be used while testing the software/application.
 List of test cases used during the testing process.
 Enumeration of features to be tested.
 List of deliverables to be tested.
 The resources allocated for testing the application.
 A schedule of tasks and milestones to be reached.
 Possible risks involved during the testing process.

Test Case

Test case is a complexity of inputs, serious of steps, and conditions that can be used during the
process of testing. The key point of this activity is to find out whether a software is successful in terms
of its functionality and other aspects. There are various types of test cases such as logical, functional,
error, negative test cases, physical test cases, UI test cases, etc.

What's more, test cases are written to keep track of the software testing coverage. Basically, there are
no formal templates that can be used while writing a test case.

Test case is a complexity of inputs, serious of steps, and conditions that can
be used during the process of testing.
However, the following components are commonly accepted:

 Test case ID.


 Product module.
 Product version.
 Revision history.
 Purpose.
 Assumptions.
 Pre-conditions.
 Steps.
 Expected outcome.
 Actual outcome.
 Post-conditions.

You might also like