Testing Approach
Testing Approach
The proposed testing process will follow the detailed testing planning and execution cycle for a System Test Life Cycle
(STLC). A brief overview of the testing planning is provided below.
1. Requirements Document.
2. Architecture and Design Documents.
3. End to End Use Cases.
4. Module / Sub-System level interfaces.
5. Security Considerations.
• Application Scenario Analysis: Study different modes in which a sub system can be configured and shall be
operating in the entire eco system. Associate modes / configurations with different users and identify all the
combinations. This provides a detailed analysis of different configurations of the sub systems for every user. This
type of analysis is very important when the systems are multi-tenant.
• Use Cases Modelling: Identify all Use Cases for every User & Application Scenarios & document all the use cases
as test scenarios
• Data Coupling and Control Coupling Analysis: Study the Architecture and Design and identify all the interfaces
at sub systems level. Model the entire solution at a black box level to understand external data input into and output
from the solution. Based on this, analyze the flow of data across internal sub systems and the way each data point
affects the state / operation of the subsystem. This ensures the data integrity is maintained and each subsystem is
robust enough to ensure there are no DOS (Denial of Service) or Data Loss possibilities.
• Succession Analysis: After all the above analysis is done, team shall analyze the existing Test Strategies, Test
Scenarios & Test Data to assess the test sufficiency achieved in the existing versions live. If there are any major gaps
identified, test team shall provide details on the gaps along with a plan to close the same. This shall be considered as
a technical debt and shall be taken as a separate phase outside the current project testing scope.
• This analysis shall specifically focus on the change modes (Change-Independent, Change Impacted,
Impacted, impacts to other feature, independent) on all features, assess the feature maturity, failure impacts
etc. to identify new test of test cases without any redundancy.
• Test Data Identification (Special Focus on Multi-Tenancy Features): This shall include the study of Tenant
Specific Data and the provisions in the solution to ensure the data protection and prevention of data corruption
aspects are considered. This also shall focus on identifying the Most optimal combination of Data and
Configurations which can provide high data coverage
• Test Cases Writing: Document all the test cases to be used for execution using the Use Cases or Test Scenarios
identified and associating with the Configurations and Data identified in previous steps.
• Test Execution & Defect Reporting: Execute the test cases as per the identified plan on the version identified for
testing. Log any defects found in the process and track as per the Defect Management Guidelines as set by
stakeholders.
• Final Sign-Off: Execute all the identified Acceptance Test cases on Target environment as agreed upon between
stakeholders and Happiest Minds team. Obtain sign-off based on meeting the PASS criteria as agreed upon
Testing Levels:
The overall testing will be carried out at 3 different levels:
API testing
Sprint Level
Component / Sub System Level Testing
E2E Integration Testing
User Acceptance Testing
API testing
This testing focusses on the validation of API data using postman to verify the API’s are working as per the
requirements.