AROBS Transilvania Software

Request info

User and Operational Acceptance Testing

These tests are performed by the end users to make sure the components and the system itself work according to the Service Level and Operation Level Agreements (SLA / OLA) signed by the parties.

User Acceptance Tests (UAT) usually take place in the final stages of the project life-cycle, right before the client accepts the new system. They are run in environments that emulate real-world usage conditions, based on predefined test cases on selected business processes, providing precious feedback to the architects, software engineers, and testers. 

Operational Acceptance Testing (OAT) is typically run by operations and / or systems administration staff  in a (simulated) environment and focuses on operational aspects (e.g. resource-behavior, ability to recover and install, and technical compliance) to ensure the system is within the specified parameters. Responsibility at this stage is typically transferred from the software development company to the Application Owner - the single point of contact for business units on issues regarding the operation of dedicated applications - and the Operation Team, which deploys and operates the software according to well-defined processes.

 Load and performance tests,  the ability of the system to perform reliably and to recover from problems,  backup recovery, data integration tests, the contingency plan for disaster recovery are a few of the aspects that make the object of OAT.

 If you rely on a different provider for software development, unit, integration, and system testing, AROBS can help you plan and run any of the following: 

  • Operational documentation review (e.g. blueprints, implementation plan, architectural overview, operational documentation, data structure explanations, business continuity plans, disaster recovery plans);
  • Dress rehearsal (used for major changes in production environments);
  • Code analysis (against quality indicators and metrics);
  • Installation testing (running application installs and uninstalls on all platforms and configurations for which it was designed);
  • Central component testing (database systems, run-time environments);
  • End-to-end testing of the operation environment;
  • Load and performance testing;
  • SLA / OLA monitoring test;
  • Backup and restore testing;
  • Security testing;
  • Fail-over testing;
  • Recovery testing.

 How can AROBS assist you?