DEV Community

Cover image for Types of Document in Software Testing
AKTHER HAMID SAYMON
AKTHER HAMID SAYMON

Posted on

Types of Document in Software Testing

Types of Document in Software Testing:

  1. Test Plan
  2. Test Scenario
  3. Test case
  4. Traceability Matrix

Test Plan:
Test Plan is a document prepared at the project level. It determines the work products to be tested, how they will be tested, and the distribution of test types among testers in general.

A Test plan is a document describing the scope, approach, objectives, resources, and schedule of a software testing effort.
It is the document that outlines the what, when, how, who more of a testing project.

Test Scenario:
A Test Scenario is a single-line statement that specifies the area in which your application will be tested.

A TEST SCENARIO (What to test) is defined as any functionality that can be tested. It is also called Test Condition or Test Possibility.

As a tester, you should put yourself in the end user’s shoes and figure out the real-world scenarios and use cases of the Application Under Test.

Test case:
A test case is a document that describes an input, action, or event, and its expected results, in order to determine if a feature of an application is working correctly.

A test case (how to test) is a document which consists of a set of conditions or actions which are performed on the software application in order to verify the expected functionality of the feature.

Traceability Matrix:
The Traceability Matrix, also known as the Requirement Traceability Matrix (RTM), is a table used to track requirements in the Software Development Life Cycle (SDLC).

Top comments (0)