 |
|
 |
 |
|
| A Fortune 50 technology company needed to comprehensively manage its flagship Configuration... Read More > |
|
 |
|
|
|
Under our comprehensive QA & Testing service portfolio, we offer the following services:
 |
Pre Release |
 |
 Unit testing: Each unit (basic component) of the software is tested to verify that the detailed design for the unit has been correctly implemented.
Integration testing: Exposes defects in the interfaces and interaction between integrated components (modules).
Functional testing: Tests at all levels (class, module, interface, or system) for proper functionality as defined in the requirement specification.
System testing: Tests a completely integrated system to verify that it meets its requirements.
System integration testing: Verifies that a system is integrated to any external or third party systems defined in the system requirements.
Performance Testing: Validates whether the quality of service parameters defined at the requirements stage is met by the final product.
Acceptance testing: Conducted by the end-user, or customer to validate whether or not to accept the product.
|
Post Release |
|
Alpha testing: Simulated or actual operational testing by potential users/customers or an independent test team at the developers' site. Alpha testing is mainly used for off-the-shelf software as a form of internal acceptance testing, before the software goes to beta testing.
Beta testing: Versions of the software, known as beta versions, are released to a limited audience outside of the programming team. The software is released to groups of people so that further testing can ensure the product has fewer faults or bugs.
Regression Testing: After modifying software, either for a change in functionality or to fix defects, a regression test re-runs previously passing tests on the modified software to ensure that the modifications haven't unintentionally caused a regression of previous functionality.
 |
|
 |
