Software Testing Consulting Services
List of all services offeredQuality Control
All the Testing activities conducted post build delivery to Quality Server/Environment belongs to Quality Control.
The objective of Quality Control activities are to find Defects to ensure Defect free Product to Customer.
The following Testing Types are performed to find the Defects.
Smoke/BAT Testing:
Execution of BAT (Build Acceptance Test) Test Cases to verify the stability of QA Build.
Post successful execution further Testings will commence else Build will be rolled back with Defects are logged for closure.
System Testing:
Execution of Test Cases which belongs to a given Release, for which the code is developed by Dev Team during that Agile Sprint or Release cycle.
Sanity Testing:
Post Defect(s) fix, re-execution of Test Cases which found the Defects to ensure that the Defects logged were properly fixed and no gaps or mismatches found.
Regression Testing:
Execution of Test Suite/Cases to ensure that the new code developed has not resulted into new Defects in the Pre-existing code (Code which is developed in previous Release/Sprint Cycles).
The Impact areas of the Application to be tested are found using Dependency and Traceability Matrix.
UAT (User Acceptance Testing):
User Test Scenarios executed to validate the Functionality of the Application under Test.
UAT Testing results to enable decision making for the Build Go/NoGo to Production/Live server.
Test Reports:
Reports and Charts are used to determine the efficiency and Productivity of Development and Testing Teams and SDLC and STLC processes.
Root Cause analysis of Defect slippage to identify the root causes of Defect Slippages to fix them.
Test/Quality Reports consists of various metrics include Team Velocity, Schedule Slippages, Defect Slippages, Defect Removal efficiency of Testing and Devlopment Teams,
Defect Density, First Pass Yield and Build Rollout Confidence Levels.
Quality Assurance
All the Testing activities conducted before the exeution of Testing Types on Quality Server/Environment Build belongs to Quality Assurance.
The objective of Quality Assurance is to develop the Testing artifacts to arrest the Defect slippage to UAT/Prod enviroments.
Test Strategy
Test Strategy is a Test Approach document to ensure optimum utilisation of Budget and resources and uniformity across Testing Teams in implementing Market best Standards.
Test Strategy document contains Scope, artifacts and templates for Test Plan, Test Cases, Treaceability Matrix and Test Metrics/Reports, Test Environment, Types of Testings,
Automation Testign selection criteria, Testing Tools, Release Control, RCA, Risk Analysis, Reviews, Approvals and Process Optimzation techniques/methodologies.
Test Plan
Test Plan is release based document consists of Who, What, When and How to test details.
Test Plan enables determining the Capacity planning and Resource shortages, Test Case development and execution scope and schedules and Testing methods includes Manual/Automation for Functional, API, Database and Performance Testings.
Test Cases
Test Case is an User interaction with the Application to verify the behaviour of the Application meets with the Customer requirements and expectations.
Treaceability Matrix
Test Cases are mapped to Test Plans and Requirement ids to enable the Change Requirement management.
Treaceability Matrix is used to identify the Test Cases set to be executed for Defects Retesting and Regression Testing.
Test Case Sufficiency
Test Case Sufficiency is ensured by 2 ways
1. Mapping of Test Cases to Requirements to ensure all Requirements are covered.
2. Ensuring all combinations of User interactions for a given Requirement using methodologies like FMEA (Failure Mode and Effects Analysis).
RCA (Root Cause Analysis)
Defects Slippage to QA, UAT and Prod environments triggers Root Cause Analysis.
The objective of this analysis is to find the root of slippages and fixing them.
Fixing/addressing of gaps leading to Defects slippage helps improve Process efficiency of Requirement gathering, Development and Testing.
QA Process Transformation / Optimization
The Objective of any Process Optimization is to reduce the efforts and increase the Productivity.
QA Process Optimization is achieved by the following
1. Defect Prevention 2. Defect Slippage Removal 3. Automation
1. Defect Prevention
Agile Devlopment Process effectively aimed at elimnating Defects.
Methodologies like BDD (Behavioral Driven Development) and TDD (Test Driven Development) to enable the Defect Prevention.
2. Defect Slippage Removal
RCA (Root Cause Analysis) for all the Defect slippages to QA, UAT and Prod environment to identify the gaps in the Process.
Fixing the gaps in Test Cases, Test Data, Tool limitations and H/W & S/W limitations.
Ensuring Test Case sufficiency with regard to coverage of all possible User interactions are Key and methodologies like FMEA are helpful.
3. Automation
Automation of Smoke and Regression Suites using an Automation Tool.
Automation of repitative activities such as Test Data Creation, Test Report email notifications, Defect Reports generation etc
FMEA (Failure Mode and Effects Analysis)
Failure Modes, Causes and Effects analysis enables listing of Application areas categorized by Risk wise (Critical, High, Medium and Low).Calculation of Risk Priority Number RPN = Severity * Probability * Detection
RPN assigned Requirements, Test areas/cases enables the expert/SME team members working on the High/Critical Risk areas of the Application.