Testing Process
Stage #1
Requirements validation
We verify the customer’s requirements and validate them based on the inputs from the clients, market surveys and research of the domain. An SRS is created which leads to designing of wire frames.
Environment setup
It includes OS versions, test devices, support apps, multiple browsers and other support to perform the testing. Our QA team perform a smoke test to check the readiness of the environment.
Test Plan
Our QA team lists the scenarios, formulate the test cases and document them. A test plan is created which defines the scope, roles, risks, entry and exit criteria and test objectives.
Stage #2
Test Design
It is a high level checklist specifying the performance and execution of tests, the way testing will be approached, valid inputs and outputs of each case.
Test execution
With our agile methodology, our QA team start testing as soon as a piece of functionality is implemented. As per the test plan, a list of tests are performed and documented over the code.
Test reporting
We use Redmine and bugzilla to evaluate the quality of the product. A regular report is submitted to client to know the status and quality of the product being developed.
Product Quality Criteria
Our standard criteria helps you reduce time to market, lower development costs, and streamline delivery.
Types of Testing
Functionality Testing
Functionality testing verifies each function of the software operates as per the requirements document. Here, the bugs are caught in the early stage of the development.
-
Smoke
-
Unit
-
Regression
Compatibility Testing
Compatibility testing check whether the developed software is capable of running under different environments and conditions as stated in the SRS.
-
OS Versions
-
Devices
-
Browsers
-
Platforms
UI Testing
GUI testing involves checking the screens with the controls like menus, buttons, icons, and all other design elements. It also checks the app is developed under android & iOS guidelines.
Performance Testing
The focus of Performance Testing is checking a software program's speed, scalability, stability, response time, resource usage.