DIVISION OR FUNCTION :DIGITAL DOCUMENT NO: DI-SQA- ISSUE DATE:31th July 2023

INNOVATION 001

VERSION: 1.0 EFFECTIVE DATE: TBA

REVISION: Nil

TITLE: SQA SOP DOCUMENT TYPE :PROCEDURE

Page 1 of 7

1. PURPOSE
The purpose of this document is to capture and record information needed to properly define and plan a project; thus,
establishing documented evidence that provides a high degree of assurance that a specific project shall consistently meet
its predetermined specifications and quality attributes.

2. APPLICABILITY
This document applies to all Entities, functions, and personnel that deal with any kind of project under ASCEND Healthcare
Solutions ownership.

3. ASSOCIATED DOCUMENTS
NA
4. DEFINITIONS

TERM DEFINITION

SQA Software Quality Assurance

5. RESPONSIBILITIES
The ASCEND HEALTHCARE SOLUTIONS PMO is accountable and responsible for managing this document.

6. APPROVALS
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.

THIS DOCUMENT CONTAINS CONFIDENTIAL AND PROPRIETARY INFORMATION OF ASCEND Healthcare Solutions.
THE USER IS RESPONSIBLE FOR VERIFYING THIS DOCUMENT IS CURRENT PRIOR TO EACH USE.
USE OF A SUPERSEDED OR OBSOLETE DOCUMENT IS PROHIBITED.
For Use Only by Affiliates Of ASCEND Healthcare Solutions.
 DIVISION OR FUNCTION :DIGITAL DOCUMENT NO: DI-SQA- ISSUE DATE:31th July 2023
INNOVATION 001

VERSION: 1.0 EFFECTIVE DATE: TBA

REVISION: Nil

TITLE: SQA SOP DOCUMENT TYPE :PROCEDURE

Page 2 of 7

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 business
Resource Usage 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 Completed system as defined by business objectives Waterfall
User Acceptance Testing

6.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

6.3. Design Procedure

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.
6.4. 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

THIS DOCUMENT CONTAINS CONFIDENTIAL AND PROPRIETARY INFORMATION OF ASCEND Healthcare Solutions.
THE USER IS RESPONSIBLE FOR VERIFYING THIS DOCUMENT IS CURRENT PRIOR TO EACH USE.
USE OF A SUPERSEDED OR OBSOLETE DOCUMENT IS PROHIBITED.
For Use Only by Affiliates Of ASCEND Healthcare Solutions.
 DIVISION OR FUNCTION :DIGITAL DOCUMENT NO: DI-SQA- ISSUE DATE:31th July 2023
INNOVATION 001

VERSION: 1.0 EFFECTIVE DATE: TBA

REVISION: Nil

TITLE: SQA SOP DOCUMENT TYPE :PROCEDURE

Page 3 of 7
should work with the appropriate person(s) to determine the test data needs. Test data should be included in the test cases or
scripts.

7. INPUTS
7.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.
7.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.

7.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

7.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.

7.5. Testing Measurements

 Number of test cases
 Number of untested test cases

7.5. Defect Measurements

 Number of defects
 Number of closed defects

8. OUTPUTS
The following is a list of different outputs expected from the different tests performed throughout the QA process.

THIS DOCUMENT CONTAINS CONFIDENTIAL AND PROPRIETARY INFORMATION OF ASCEND Healthcare Solutions.
THE USER IS RESPONSIBLE FOR VERIFYING THIS DOCUMENT IS CURRENT PRIOR TO EACH USE.
USE OF A SUPERSEDED OR OBSOLETE DOCUMENT IS PROHIBITED.
For Use Only by Affiliates Of ASCEND Healthcare Solutions.
 DIVISION OR FUNCTION :DIGITAL DOCUMENT NO: DI-SQA- ISSUE DATE:31th July 2023
INNOVATION 001

VERSION: 1.0 EFFECTIVE DATE: TBA

REVISION: Nil

TITLE: SQA SOP DOCUMENT TYPE :PROCEDURE

Page 4 of 7
8.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.

8.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.

8.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
8.4 System Testing
System testing is complete when the following criteria are met:
 Test cases are executed for the scope as defined in the test plan.
 All critical and major defects resolved or postponed to the next build.

9. SQA Time Estimation

Story size Work effort

X-small 2 hours
small 4- hours
Medium 8- hours
Large 2-3 days
.

THIS DOCUMENT CONTAINS CONFIDENTIAL AND PROPRIETARY INFORMATION OF ASCEND Healthcare Solutions.
THE USER IS RESPONSIBLE FOR VERIFYING THIS DOCUMENT IS CURRENT PRIOR TO EACH USE.
USE OF A SUPERSEDED OR OBSOLETE DOCUMENT IS PROHIBITED.
For Use Only by Affiliates Of ASCEND Healthcare Solutions.
 DIVISION OR FUNCTION :DIGITAL DOCUMENT NO: DI-SQA- ISSUE DATE:31th July 2023
INNOVATION 001

VERSION: 1.0 EFFECTIVE DATE: TBA

REVISION: Nil

TITLE: SQA SOP DOCUMENT TYPE :PROCEDURE

Page 5 of 7

9. Testing Performa

Time Types
1 hour – 2 hours  Regression testing
 Performance 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

THIS DOCUMENT CONTAINS CONFIDENTIAL AND PROPRIETARY INFORMATION OF ASCEND Healthcare Solutions.
THE USER IS RESPONSIBLE FOR VERIFYING THIS DOCUMENT IS CURRENT PRIOR TO EACH USE.
USE OF A SUPERSEDED OR OBSOLETE DOCUMENT IS PROHIBITED.
For Use Only by Affiliates Of ASCEND Healthcare Solutions.
 DIVISION OR FUNCTION :DIGITAL DOCUMENT NO: DI-SQA- ISSUE DATE:31th July 2023
INNOVATION 001

VERSION: 1.0 EFFECTIVE DATE: TBA

REVISION: Nil

TITLE: SQA SOP DOCUMENT TYPE :PROCEDURE

Page 6 of 7

10. PROJECT AND TESTING TYPES

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
 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

THIS DOCUMENT CONTAINS CONFIDENTIAL AND PROPRIETARY INFORMATION OF ASCEND Healthcare Solutions.
THE USER IS RESPONSIBLE FOR VERIFYING THIS DOCUMENT IS CURRENT PRIOR TO EACH USE.
USE OF A SUPERSEDED OR OBSOLETE DOCUMENT IS PROHIBITED.
For Use Only by Affiliates Of ASCEND Healthcare Solutions.
 DIVISION OR FUNCTION :DIGITAL DOCUMENT NO: DI-SQA- ISSUE DATE:31th July 2023
INNOVATION 001

VERSION: 1.0 EFFECTIVE DATE: TBA

REVISION: Nil

TITLE: SQA SOP DOCUMENT TYPE :PROCEDURE

Page 7 of 7

11. APPROVALS

NAME ELECTRONIC SIGNATURE DATE

Awais Hamid 07-Aug-2023

Sajjad Haider
Danial Ghazali

Mustafa Gul

THIS DOCUMENT CONTAINS CONFIDENTIAL AND PROPRIETARY INFORMATION OF ASCEND Healthcare Solutions.
THE USER IS RESPONSIBLE FOR VERIFYING THIS DOCUMENT IS CURRENT PRIOR TO EACH USE.
USE OF A SUPERSEDED OR OBSOLETE DOCUMENT IS PROHIBITED.
For Use Only by Affiliates Of ASCEND Healthcare Solutions.