Test Engineering & QA

We provide stand alone test engineering and software quality assurance services. For testing and QA, we use the same approach, methodology, and tools that we use for our custom application development and integration services, which are summarized below:

Approach
Test Cases Preparation
Test Execution & Bugs Reporting
Release to Production

Approach

The scope of software testing often includes examination and execution of code in various environments and conditions. A testing team may be separate from the development team.

We have a well-defined testing life cycle, which is applicable to all testing scenarios, and ensures that we:

Obtain all relevant inputs
Carry out planning adequately
Perform executions as planned
Obtain, review, and monitor results
Define interfaces into the overall quality management processes and project delivery phases

The test plan document consists of the following information:

Total number of features to be tested
Testing approaches to be followed
Testing methodologies
Number of man-hours required
Resources required for the whole testing process
Testing tools that are to be used
Test cases, etc.

The test design is represented pictographically with the test stages summarized as:

Identify different modules of the software
Identify the paths connecting all the modules

Then the design is drawn. The test design is the most critical one, which decides the test case preparation, assessing the quality of the testing process.

Test Cases Preparation

Test cases should be prepared based on the following scenarios:

Positive scenarios
Negative scenarios
Boundary conditions
Real world scenarios

Test Execution and Bugs Reporting

Once the unit testing is completed and the code is released to QA, the functional testing is done:

Top-level failures testing is done at the beginning
If any top-level failures occur, the bugs will be reported to the developer immediately to get the required workaround
The test reports will be documented properly and the bugs have to be reported to the developer after the testing is completed

Release to Production

Once the bugs are fixed, another release is given to QA with the modified changes:

Regression testing is executed
Once QA assures the software, the software is released to production
Before releasing to production, another round of top-level testing is done
The testing process is an iterative process, retesting after bugs are fixed