 |
| Unit Testing (White Box) |
- Typically done by the developer using unit test cases
- Each functionality is tested alone
|
| Integration Testing |
- Units that have already been tested are integrated into a component or module and the interface between them is tested
|
| Functionality Testing (Black Box) |
- Customizable, highly offshore centric and cost-effective
- Validates that application conforms to functional specifications like
- Business Rules
- Processing Logic
- Correctness of all computations
|
| Non-Functional Testing |
- Load/performance testing
- Localization & Internationalization
- Usability testing
- Installation testing
|
| Regression Testing |
- Done when the application is developed with multiple builds
- Checks whether previously tested functionalities still function
|
| Performance Testing |
- The primary objective is to check the scalability and peak performance of the application
- Checks parameters like: response time, availability and throughput
- Includes stress and volume testing
|
| System Test |
- Refers to the testing in artificial conditions
- Ensures that system performs as expected and as required
|
| User Acceptance Testing |
- Acts as a final quality gateway, where any defects not detected in system test may be picked up
- Test procedures that lead to formal 'acceptance' of a new or changed system
|
| Implementation & Deployment Testing |
- Ensures that the application after implementation is functioning as per requirement
- Verifies that the move the live environment is successful
|
| Localization and Internationalization |
- Ensures that services/products work appropriately in different locales
|
| |