QA White-box Testing

Our expertise encompasses the following disciplines:

  • Recovery and Failover Testing — Recovery testing will force the failure of major components to verify that recovery is properly performed. Typical tests could include:
    • While an application is running, suddenly restart the computer, and afterwards check the validity of the application's data integrity.
    • While an application is active, disable the network connection. After some time has elapsed, re-enable the network connection and verify that the application continues to receive data from the point at which the network connection was disabled.
  • Application Integration Testing
    This testing is performed to verify functional and reliability requirements placed on major components of the system. Test cases will be written to verify that all major components within system interact correctly.
  • API Testing — API testing is a type of white-box testing that runs tests against an API rather than the traditional GUI. Such tests are done to validate that the API adheres to the documentation or conforms to a specification.
  • Security Testing — This testing is done to determine whether the application/system protects data and maintains functionality as intended. This testing covers confidentiality, integrity, authentication, authorization, availability, and non-repudiation.
  • Installation Testing — This testing follows what a customer will need to do to install and configure new software successfully. The testing process may also involve full or partial upgrades.
  • Automation — Automation of test cases, including functional test cases, is crucial. Automation frees up your test engineers to focus on high value testing, finding new issues.
  • Regression testing — This testing is performed to uncover regressions in the application. Regressions may occur whenever functionality that was working correctly in the past, stops working following a new builds.