Our QA processes involve rigorous verification and validation methodologies to reduce defects at every stage of the SDLC. The way we systematically test software functionality, performance, security and other characteristics leverages the combined strength of our technological skills, domain knowledge, process focus and commitment to quality.

Our well-defined QA methodologies allow us to practice component-based approach with emphasis on repeatability and reusability resulting in accelerated project cycles and enhanced quality.

We perform informal and formal testing. Business process team conducts informal testing during configuration when processes are prototyped and configuration options are reviewed. Developers also conduct informal unit testing as various enhancements, reports, data conversions, and interface programs are developed. Our QA process runs from major phases of testing mentioned below.

• Unit Testing: This involves verification effort on the smallest unit of software design. Using the component-level design description as a guide, important control paths are tested to uncover errors within the boundary of the module.
• Functionality Testing: This involves validating software to check whether it conforms to its specifications and correctly performs all its required functions. It entails a series of tests that perform a feature-by-feature validation of behaviour using a wide range of normal and erroneous input data.
• Integration Testing: It is conducted on complete, integrated software to validate the software's compliance with its specified requirements. During integration testing, one focuses solely on the outputs generated in response to inputs provided and execution conditions rather than verifying internal structure of the program/ system.
• Performance Testing: This involves testing the software against performance requirements such as response time, availability and throughput. These include stress, load and volume testing. The performance testing is performed using industry-standard tools.
• User Acceptance Testing: This includes testing the software based on business requirement specifications. User Acceptance Testing (UAT) checks the software against the ‘Requirements’ and validates that software has delivered what was initially requested.

While executing test, we follow subsequent goal sets for various kinds of tests. The objective is defined for each major area to be tested during test process. Our test strategy is accountable for each area to verify and validate that the system meets functional and operational requirements before it is deployed. We are committed to a disciplined project life cycle that consistently produces quality software and services that are on time and within budget.