SQA SOP
SOP- V1.0
Page: 1/7
Software (QA) Testing
Standard Operating Procedure
Software Quality Assurance Testing
SOP- V1.0
Revision A
8/3/2023
ASCEND
Confidential and Proprietary, All rights reserved.
IMPORTANT NOTE: This document contains confidential information…
Documentation History
Date Rev Author Comments
6/13/16 A R G Coles Initial Release
ASCEND Confidential and Proprietary, All rights reserved
SOP – v1.0 Revision A
SQA SOP
SOP- V1.0
Page: 2/7
Software (QA) Testing
Approvals
Authors: Approved by:
Name(s): Name:
Date:
Name:
Date:
Name:
Date:
Name:
Date:
Name: Date:
Name:
Date:
Name:
Date:
Table of Contents
Documentation History...................................................................................................................................................... 1
Approvals.......................................................................................................................................................................... 2
1. Test Stages......................................................................................................................................................... 3
2. Test Case Designs................................................................................................................................................... 4
2.1 Design Procedures........................................................................................................................................... 4
2.2. Test Data.......................................................................................................................................................... 4
3. INPUT......................................................................................................................................................................... 4
3.1 Test Plans......................................................................................................................................................... 4
3.2 Test Cases........................................................................................................................................................ 4
3.3 Test Completion Criteria................................................................................................................................... 4
3.4. Defects Classification...................................................................................................................................... 4
3.5. Testing Measurements..................................................................................................................................... 5
3.6. Defect Measurements...................................................................................................................................... 5
4. OUTPUTS................................................................................................................................................................... 5
4.1 Unit Testing............................................................................................................................................................ 5
4.2 Functional Testing.................................................................................................................................................. 5
4.3 Integration Testing................................................................................................................................................. 5
4.4 System Testing...................................................................................................................................................... 5
5. Bugs size estimation:.................................................................................................................................................. 5
Testing Performa:............................................................................................................................................................ 5
ASCEND Confidential and Proprietary, All rights reserved
SOP – v1.0 Revision A
SQA SOP
SOP- V1.0
Page: 3/7
Software (QA) Testing
6. Project type and testing............................................................................................................................................... 6
1. Test Stages
Agile testing is a continuous process and has many parts. Below is a short list of reasons for these test stages.
Test activities must be integrated in the development process. This means that testing is not a
separate phase, rather a continuous activity of an agile team.
All team members must be prepared to perform test activities. Although the team should contain
professional QA Engineers, this does not mean that all test activities can be carried out by QA
Engineers alone.
Stage of Test Deliverable Verified
Unit Testing Code for a unit
Functional Testing Functionality of a component within a system
Usability of the software
Data validation and data storage
Integration Testing Code for related components or sub-systems
Interactions among the components
Conformance of interface requirements
Security validation between the components
Data integrity between the components
Stress, Volume, Validate data rates & volume
Performance, and Achieve performance that mimics realistic
Resource Usage business usage, loads and timing
Testing Validate stability of System under “overload”,
extreme and abnormal conditions
Verify resource consumption does not exceed
required level, system not particularly Agile SDLC
sensitive to certain input values
Validate system can meet acceptable service
levels
Completed system as defined in requirements and
System Testing
design specifications
Customer User Acceptance Completed system as defined by business Waterfall
Testing objectives
2. Test Case Designs
Test cases should be derived from the use case and feature design. If the use cases do not address tests such as
boundary, equivalence partitioning, etc., additional test cases should be created to test these conditions.
The following are Test Case Naming Conventions:
Test Case Parent – TC1, TC2
ASCEND Confidential and Proprietary, All rights reserved
SOP – v1.0 Revision A
SQA SOP
SOP- V1.0
Page: 4/7
Software (QA) Testing
2.1 Design Procedures
All test scripts should be written as detailed as possible. The test lead should work with both the Project Manager and
Product Owner to determine the level of detail in test scripts.
2.2. Test Data
In order to test a software application, you need to enter some data for testing most of the features. The Test
Manager or Analyst should work with the appropriate person(s) to determine the test data needs. Test data should be
included in the test cases or scripts.
3. INPUT
3.1 Test Plans
A test plan is a document detailing the objectives, target market, internal beta team, and processes for a
specific beta test for a software or hardware product. The plan typically contains a detailed understanding of
the eventual workflow.
A test plan lets you specify what you want to test and how to run those tests. A test plan can be applied to a
specific iteration of your project. You can have just one default test suite for your test cases, or you can create
a test suite hierarchy.
3.2 Test Cases
A test case is a set of conditions under which a tester will determine whether an application, software system or
one of its features is working as it was originally established for it to do.
3.3 Test Completion Criteria
Testing is considered complete when all of the following is achieved:
Acceptance criteria has been met
All test scripts have been successfully executed
3.4. Defects Classification
All issues/defects can be classified as a type of severity, whether it’s Critical, major, minor, or cosmetic. These
issues can be broken down further and are explained in Appendix A.
3.5. Testing Measurements
Number of test cases
Number of untested test cases
3.6. Defect Measurements
Number of defects
ASCEND Confidential and Proprietary, All rights reserved
SOP – v1.0 Revision A
SQA SOP
SOP- V1.0
Page: 5/7
Software (QA) Testing
Number of closed defects
4. OUTPUTS
The following is a list of different outputs expected from the different tests performed throughout the QA process.
4.1 Unit Testing
Unit testing is complete when the following criteria are met:
Unit test is conducted, and issues resolved (Development)
Test results and deliverables are provided to the team
4.2 Functional Testing
Functional testing is complete when the following criteria are met:
Features and capabilities work the way the Product Owner intended.
User acceptance tests validate the aggregate behavior of many user stories The system
meets both usability and functionality requirements.
4.3 Integration Testing
Integration testing is complete when the following criteria are met:
Outstanding defects logged in the defect tracking tool.
All integration test cases scripts have been successfully executed.
Test results and deliverables provided to the test team
4.4 System Testing
System testing is complete when the following criteria are met:
Test cases executed for the scope as defined in the test plan
All critical and major defects resolved or postponed to the next build
5. Bugs size estimation:
Story size Work effort
X-small 2 hours
small 4- hours
Medium 8- hours
Large 2-3 days
Testing Performa:
Time Types
1 hour – 2 hours Regression testing
Performance testing
ASCEND Confidential and Proprietary, All rights reserved
SOP – v1.0 Revision A
SQA SOP
SOP- V1.0
Page: 6/7
Software (QA) Testing
Backward compatibility
4hour – 6 hours System testing:
Black box testing
Sanity testing
Monkey testing
Happy path testing
Ad-hoc testing
8 hour- 16 hours System testing:
End-to-end testing
Black box testing
Sanity testing
Monkey testing
Happy path testing
Performance testing:
Load testing
Stress testing
Scalability Testing
Volume testing (flood testing)
Endurance Testing (Soak Testing)
Integration testing:
Gray box testing
UI/UX:
Usability testing
Responsive testing
Acceptance test
6. Project type and testing
PROJECT TYPES TESTING TYPES
Bug fixing: Unit testing
Component testing
Regression testing
Sanity testing
New module: Regression testing
Performance testing
Backward compatibility
Ad-hoc testing
Integration testing
Update: System testing:
End-to-end testing
Black box testing
ASCEND Confidential and Proprietary, All rights reserved
SOP – v1.0 Revision A
SQA SOP
SOP- V1.0
Page: 7/7
Software (QA) Testing
Sanity testing
Monkey testing
Happy path testing
Performance testing:
Load testing
Stress testing
Scalability Testing
Volume testing (flood
testing)
Endurance Testing
(Soak Testing)
Addition features: System testing:
End-to-end testing
Black box testing
Sanity testing
Monkey testing
Happy path testing
Integration testing:
Gray box testing
UI/UX testing: Usability testing
Responsive testing
ASCEND Confidential and Proprietary, All rights reserved
SOP – v1.0 Revision A
