- Home
- Business Services
- Quality Assurance
- QA Levels
QA Levels
Our QA process is divided into different levels of teams to ensure complete QA coverage. Each QA team focuses on its specialty level. Once all the levels of QA are successfully completed, the Idha QA process is complete
Each level of testing falls under two broad categories.
Black Box Testing
This type of testing is based on requirements and functionality.
Knowledge of application design.
White Box Testing
This type of testing is based on coverage of code statements, branches, paths and conditions.
Knowledge of internal logic of application is required.
Functional Testing
This is a black box testing type that verifies application functionality is working as per requirements.
Usability Testing
Black box testing that test for user friendliness. Ensure the user interface is properly designed for a positive end-user experience.
Compatibility Testing
Testing to ensure application compatibility with different OS and browsers.
Integration Testing
Testing to ensure distinct components of the application work in accordance with customer specifications after product integration.
System Testing
Upon completion of integration testing, system testing is conducted to ensure integrated product work according to specifications on the environment designed.
Regression Testing
Testing to ensure that the application remains intact during defect fixes and new enhancements.
Sanity Testing
When partial builds are integrated into the application, sanity testing is performed to ensure the updates modules works with the existing.
Performance Testing
Performance Tests are tests that determine end-to-end timing (bench marking) of various time critical business processes and transactions, while the system is under low load, but with a production sized database.
Scenario Testing
Scenario Testing employs a specific series of steps or conditions that individually may not reveal a defect, but together may do so.
Error Handling Testing
An error handling test explores an application when specific errors are introduced and the behavior of the application is observed.
Field Entry Testing
Field entry testing examines data that is entered in screen forms intended for database input. Testing includes data values, ranges, invalid input, GUI controls, error recovery and any processing that might occur as a result of data input.
Database Testing
Database testing validates that data written to and read from a database is correct. Any processing, conversion and data recovery situations should be explored.
End-to-End Testing
End-to-End Testing investigates the final expected results with data or process, flow from the very start of a process to the very end.
Automated Testing
Automated Testing utilizes tools and techniques that minimize or do not require operator input, analysis or evaluation in order to perform a software inspection.
Quality Assurance
Download Collaterals
QA Datasheet
QA Brochure