Software Testing Documents


Software Testing Documents...

> Documentation is an important role before and during Testing of Software.

> Testing Documentation involves the documentation of artifacts that should be developed before or during the Testing of Software.

Documents that can be referenced for Software Testing include:

1) Project Plan
2) Requirements Specifications
3) High Level Design Document
4) Detail Design Document
5) Development and Test Process Standards
6) Corporate Standards and Guidelines

Software Testing Documents that we prepare before or during Testing of Software:

i) Test Policy (Company Level Document)
ii) Test Strategy (Company Level Document)
-------------------
i) System Test Plan
ii) Test Scenario
iii) Test Case
iv) Test Data
v) Requirements Traceability Matrix
vi) Defect Report
vii) Test Metrics
viii) Test Summary Report Etc...

Note: These are Standard Documents, some companies may use some documents only, and some companies may use extra documents also apart from these Documents.
----------------------------------------------------
In Testing Documentation, 2 important things,
i) Template
ii) Document

And Test Documentation Templates may vary from One Company to another, sometimes one project to another.

We follow Manual Documentation Process or Automation process using any Test Tools, based on our Company Test Environment...
----------------------------------------------------
i) Test Policy

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

ii) Test Strategy

> A high-level description of the Test Levels to be performed and the Testing
  those levels for an organization  (One or more Projects)

Note: One Test Policy for an Organization, and may be multiple Test Strategies,
Ex: One Strategy for Banking Applications, another for Telecom Applications etc...
----------------------------- 
i) System Test Plan

We have multiple stages of Testing, so multiple Test Plans,
Example: Unit Test Plan, and System Test Plan etc...

A Test Plan addresses one level but Master test Plan addresses multiple levels
of Testing...

Our Test Plan is System Test Plan...

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

i) Test Plan Template
----------------------------------------------------
i) Test Plan ID: 
Some type of unique company generated number to identify this test plan.

2) Introduction: 
Describe the purpose of the Plan, possibly identifying the level of the plan 
System Test Plan etc.). This is essentially the executive summary part of the plan.

3) Test Items:
These are things you intend to test within the scope of this test plan.

4) References:
List all documents that support this test plan. Refer to the actual version/release
number of the document as stored in the configuration management system.

5) Features to be Tested:
This is a listing of what is to be tested from the Users viewpoint of what the 
system does. This is not a technical description of the software, but a Users view of the functions.

6) Features not to be Tested:
This is a listing of what is NOT to be tested from both the Users viewpoint of 
what the system does and a configuration management/version control view. This is not a technical description of the software, but a Users view of the functions.

7) Test Approach:
This is your overall test strategy for this test plan; it should be appropriate to 
the level of the plan (master, acceptance, etc.) and should be in agreement with all higher and lower levels of plans. Overall rules and processes should be 
identified.
    
8) Entry Criteria:
It describes when to start Testing 

9) Exit Criteria:
It describes when to stop testing

10) Suspension Criteria:
It describes when to stop testing temporarily. 

11) Roles & Responsibilities
Team Lead or Test Lead and Team members Roles and Responsibilities.

12) Schedule:
Schedule for all Test activities in this Software Test Process.

13) Training:
Training on the application/system (Domain Training)
Training for any Test Tools to be used.

14) Test Environment / Lab:
It describes Require Hardware and software for setting-up Test Environment or 
Test Lab. 

15) Test Deliverables:
Lists out that what is to be delivered as part of this plan?

16) Approvals
Who can approve the process as complete and allow the project to proceed to the next level.

17) Glossary:
Define terms and acronyms used in the document, it can be used to understood the terms used in this plan.
----------------------------------------------------
ii) Test Case Template

A set of input values, execution preconditions, expected results, execution post
conditions, developed for a particular objective or test condition. 

1) Test Case Id: a Unique name/number (Alphanumeric)

2) Test Case Name: Name of Test Case

3) Test Suite ID: Unique name/number (Alphanumeric)

4) Pre-Condition: Status before Test Case Execution

5) Steps: Steps for Executing the Test Case

6) Post-Condition: Status After Test Case Execution

7) Expected Result: Expected Result as per Requirements

8) Actual Results: <After Test Case Execution>

9) Test Results: <After Test Case Execution and After Comparison of Expected with Actual Results> Pass / Fail

10) Remarks: Comments (Optional)
----------------------------------
Note: 
> We prepare this Test Case Template in Excel Sheet

> Test Case Template may vary from one company from another and one project to another.

> In the above template Actual Results and Test Results fields can be filled in 
  Test Execution phase, Remaining fields in Test Design phase.
----------------------------------------------------
iii) Defect Report Template:

> A defect report documents an anomaly discovered during testing. It includes all the information needed to reproduce the problem.

1) Defect Id: Any Unique name for Identifying the Defect (Alfa numeric)

2) Defect Description: Details about the Defect

3) Test Case Id: Corresponding Test Case Id for tracking

4) Tester: Tester's name (who found the Defect)

5) Product Version: Version of the Product on which defect was found

6) Build Version: Version of the Build on which defect was found

7) Priority: Importance of the Defect based on Business /Customer

8) Severity: Importance of the Defect based on Functionality

9) Status: Status of Defect
(New/Open/Fixed/Rejected/Reopen/Closed) 10) Reproducible or Not: Yes / No

    If Reproducible:
      Steps: 

    If not Reproducible:
      Attachments

11) Reporting to: Corresponding Developer

12) Remarks: Comments (Optional)
----------------------------------------------------------------------
Software Testing Videos (Manual Testing, Selenium, UFT/QTP, Live Project, Java, SQL, Python, VBScript, and FAQ)

1) Selenium Step by Step Videos
https://www.youtube.com/playlist?list=PLyGqUe6Oa_5Elc-Dv9jPzHKDx-m2GvMOd



4) Manual Testing Videos

5) UFT/QTP Videos
6) Java Videos

7) SQL Videos

8) Python Videos

9) Career Guidance

10) Introductions

12) Selenium Live Project

13) VBScript for UFT/QTP

14) Software Testing Interview Questions

15) Software Testing Practical

16) Selenium Detailed Videos

17) Health and Fitness Videos

18) TestNG Testing Framework for Selenium

19) Selenium Tutorials for Beginners…

20) Selenium Real Time Project...

21) Robotic Process Automation...

22) Selenium WebDriver Tutorials
---------------------------------------------------------------
Software Testing Resumes...

Domain Knowledge for Software Testers

UNIX Knowledge for Software Testers

SQL For Software Testers...

Software Testing Interview Questions and Answers...
---------------------------------------------------------------

0 comments:

Post a Comment