Скачать или смотреть Software Test Documents

https://www.gcreddy.com/2013/01/test-...
Software Test Documents

Documentation is an important activity in Software Testing, before, during and after Testing we create and use several documents.

Business Requirements Specification, Software Requirements Specification etc, documents are not Test Documents, they are used for Software Testing...

1. Test Policy (Company Level Document)

A high level document describes principles, approach and major objectives of the organization regarding Testing.

Test policy gives the organizational insight for the test activities,and this Test Policy can be used for both development and maintenance projects.

2. Test Strategy (Company Level Document)

A high level document of the Test Levels to be performed and the Testing within those levels for an Organization.

The test strategy is usually written by the test manager and the project manager in the top level organization.
It is generally prepared in large scale projects and does not need much updating.

In small scale projects, test strategies and test approach may be included in the test plan, and also the test strategy document may not be written separately.

3. System Test Plan

A document describing the scope, approach, resources, and schedule of intended activities

Test plan is usually prepared by the test manager or test leader in the test organization and shared with the entire team in the project.

It is a living document throughout the project and should be kept under revision control as it’s updated.

4. Requirements Traceability Matrix

This is the document that connects the requirements to the test cases.

The connection or mapping of the requirements to test cases is many to many.

This means that one requirement is tested by one or more test cases. Conversely, it is possible to have one test case addressing one or more requirements.

5. Test Scenario

An item or event of a component or system that could be verified by one or more Test cases.

How to create Test Scenarios:

Read the Requirement Documents System Under Test (SUT.. You could also refer uses cases, books, manuals, etc.

Figure out possible users actions and objectives for each requirement.

Once you have listed all possible Test Scenarios, a Traceability Matrix is created to verify that each & every requirement has a corresponding Test Scenario.

6. Test Case

A set of input values, execution preconditions, expected result and execution post conditions developed for a particular objective or Test condition.

Testers document Test cases using Test Scenarios, and using company priscribed template or organization using any Test tool for Test management then Testers write Test cases using the test tool.

Test Case writing is a most important job responsibility for testers, Test can be written for different test type, example,

Functional Test cases, Database Test cases, Performance Test Cases, Usabilitytest Cases etc, and Positive and Negative Test cases for every Test type.

7. Test Data

Data that exits before a test is executed and that effects or is effected by the component or System under test.

Test data is not required for all Test cases, using differnt sources Testers collect Test Data.

Testers create some test data as their own, collect some test data from customers and some Test data from developers.

Valid Test data can be used for Positive Testing and Invalid data for Negative Testing.

8. Test Metrics

Software testing metrics - Improves the efficiency and effectiveness of a software testing process. Software testing metrics is the quantitative indication of extent, capacity, dimension, size of some attribute of a process or product

Test Metrics helps to achieve cost savings by preventing defects, improve overall project planning, and Facilitates to understand if the desired quality is achieved

The general software testing metrics are divided into three categories Coverage, Progress and Quality.

9. Defect Report

A document reporting of any flaw in a component or System that can cause the component or system to fail to perform its required function.

Software Testers Report Defects in Test Execution of Software Test Life cycle, they may use manual Process or use any test tool like Bugzilla based on their Project Test Environment.

Testers Report defects, Developers fix defects and Testers only close defects after confirmation.

10. Test Summary Report

A document summarizing testing activities and Result. It also contains evaluation of the corresponding test items against exit criteria.

Test Summary Report summarizes the results of all testing activities.

Test Summary Report can be prepared by Test lead or Test manager at the end of Testing project.