0% found this document useful (0 votes)
4 views11 pages

Comprehensive Software Testing Process Guide

The document summarizes a software testing process. It includes steps like developing a test plan and test cases, testing in different environments, identifying and logging defects, and a post-shipment review. Following the process helps deliver a quality product on time by systematically evaluating the software, ensuring quality, and certifying the product is bug-free. Key activities include preparing test strategies and plans, writing test cases, setting up test environments, conducting testing, and defect tracking.

Uploaded by

api-3710034
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
4 views11 pages

Comprehensive Software Testing Process Guide

The document summarizes a software testing process. It includes steps like developing a test plan and test cases, testing in different environments, identifying and logging defects, and a post-shipment review. Following the process helps deliver a quality product on time by systematically evaluating the software, ensuring quality, and certifying the product is bug-free. Key activities include preparing test strategies and plans, writing test cases, setting up test environments, conducting testing, and defect tracking.

Uploaded by

api-3710034
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPT, PDF, TXT or read online on Scribd

Testing Process…

Testing Means…
• We Evaluate the Product
• We Ensure for Quality
• We Certify, that it is “BUG FREE” Product.
Kick Off Meet
Process Flow… (DT, PT, CM, IT, Compliance)

Development In progress Preparation of Test Plan/Test Case

Handoff from DT to Testing

Code Transfer to a SIT


Or in CD By CM

Mail from CM Once the Code


Is Transferred

Testing in progress

Defect Identification & Logging

Shipment or Signoff

Post Shipment Review Meeting


Testing Starts with…
• Preparation Test Strategy
• Arriving at a Test Plan
• Knowledge Transfer (KT) from Functional
Experts
• Preparing the Test Cases
• Setting up the Test Environment
– URL/ Login Id’s/ Defect Management Tool
What does a Test Plan contain?
• Target Audience
• Objective of the document
• References
• Scope of Testing – No of Pass
• Deliverables
• Exit Criteria/Sign-off
• Resources/Roles and responsibilities
• Defect Reporting
• Testing Schedule
Writing of Test Cases
BR – Business Requirements

FS – Function Specifications Clarification


Document??
Functional Points

Test Condition

Test Cases

Test Scripts or Test Steps


Test Case Template
[Link] Test Case Test Case Expected Actual Pass Fail
ID Description Result Result

1 1 Enter an System should


Invalid ID or not accept
Password invalid ID &
Password
To Accept Testing of project…
• Sufficient Time & Resources should be provided
for testing, as stated in the Test Plan
• Test Plan Approved by the PM
• Unit Test Cases from the DT
• Free Flow test ensured from DT
• Proper Environment Setup & Support
• Code Transfer through CM
• Handoff from DT
What do we achieve by
Following Process?
• Will be able to deliver a “Quality” Product ,
on “Time”
• Will be helpful at time of Audits
Are we Following??
Thank You.

You might also like