Process and Quality Assurance

Approach & Methodology:
Quality Assurance Testing Methodology is precisely defined at NGBM. Project Management, Maintenance of Time Schedules, Quality Assurance, and Software Engineering are some of the key areas we focus on in the Software Development Life Cycle process. Our exhaustive Methodology ensures thorough and effective QA Testing of the software products and applications.

Every project requires specific domain knowledge and our Project Managers work closely with each client to gather, gain and transfer that information to our testing teams. Our QA engineers quickly become product experts for each application with which they work. It is this commitment not only to proven quality assurance methods, but to our clients' business rules and processes that separate our testing activities from other third party groups.

NGBM follows T4 Quality Test Model (Test Early, Test Iteratively, Test Automatically and Test with Process).

At NGBM we follow varied methods of testing to improve our QA process.

Data Integrity Testing
Data integrity testing, a key component of QA testing, is done to verify the reliability of data storage and retrieval methods to ensure that the data obtained is in the required format, and is reliable and consistent with the defined output. Data Integrity Testing ensures that all relevant information is stored in the right place in the right manner to avoid data loss or data mismatch, which can prove to be catastrophic to any business. Parameters are customized to specific requirements of each project during the setup phase itself.

Functionality Testing / Defect Analysis
The Functionality and Defects Analysis tests are performed on the basis of the post design (pre-development) functional documentation prepared by the development team and approved by project managers to ensure cent percent conformity of the usability of the functions in relation to the business objectives of our project/product owners/sponsors. A thorough review of the entire application is performed on the anvil of the functionality/defects analysis tests by our QA testing team. The analysis of these defects and bugs are carefully documented and reviewed against our quality standards to improve our systematic methodology of internal documentation, reporting, and resolution of defects and bugs detected during the various testing processes to service our clients better.

Performance Testing
Performance testing is done to ascertain the level of performance of all the planned user cases and intended workflow in the normal working environments. Performance test would:

• Measure response time of critical transactions.
• Measure response time along with metrics such as memory and CPU cycle utilization.
• Monitor and control data collection tasks on different target systems and platforms.
• Incrementally add additional users to determine load capability.
• Monitor the performance of distributed components, such as Back-End, Middle-tier, and Client.
• Stress Testing

Stress testing, the hardest and most complex category of testing to accomplish, deals with the quality of the application in the given environment. The idea is to create an environment more demanding of the application than the application would experience under normal workloads. The major parameters typically tested are storage, retrieval, computing time and communication capacity. This process drives the system to the very limits of its endurance in order to determine what features in the application design can fail during implementation. The features that do fail can turn out to be defects capable of causing disastrous failure. One of the most time-proven and indigenous ways of achieving this is to have the test environment established at multiple testing stations. At each station, a script is exercising the system. These scripts are based on the level of regression required of the system and are specific to each application. More and more stations are added, all simultaneously hammering on the system, until the system breaks. The system is repaired and the stress test is repeated until a level of stress is reached that is higher than expected to be present at a customer site.

Compatibility Testing
Compatibility testing addresses concerns regarding a product’s capability to interface with other software and hardware. NGBM is equipped to test Client products across a varied range of software and hardware platforms to evaluate the related issues involved in Compatibility Testing.

Usability Testing
Usability testing is done to objectively evaluate a system’s ease of use and the level of convenience it provides, to fully leverage the various tools and functionalities offered by the system and to draw the maximum benefit from the system. Usability Testing further entails detailed analysis of the navigation system, the user interfaces, etc.

Click here to learn more about our Quality Assurance (QA) and Testing Approach and Methodology.