Operational Acceptance Testing


Operational Acceptance, or sometimes referred to as Operational Acceptance Testing (OAT) is critical in ensuring that the solution can be supported in production post go-live.

With DevOps becoming more common, this type of testing is incorporated earlier on in the delivery lifecycle, ensuring that the supportability of the platform is possible. Part of Service Management Planning, these tests are critical for the seamless transition into a BAU service of the solution and is key for the ongoing maintenance and support of the solution.

Accuteque has experience in many areas of operational and readiness testing. See below for the different elements of Operational Acceptance Testing that we can help undertake to ensure your systems are sustainable, supporting your business continuity.

Monitoring and Alerting

Once you have gone live with a solution it is critical that you have confidence that monitoring is working. Testing of the Monitoring and Alters throughout the delivery model are becoming more common when teams are practicing within a DevOps model.

However, when teams do not have this ways of working, stand-alone Testing of the Monitoring and Alters is needed.

This testing ensures that transactional monitoring along with system wide monitoring is in place and is able to be integrated into the wider organisational monitoring solutions.


Ensuring that a server, network or software can be patched once in a productive state.

Patch updates delivered from the vendor are required throughout the life of the software.

Being able to patch the solution without having to undertake a large project is critical for maintaining the software, particularly for security patches.

This testing ensures that you can patch a server in production. This will identify what type of outage would be required, providing confidence that this can occur in production within an outage window, reducing the impact on the business.

Release & Installation Testing

Most software systems have installation procedures that when followed render the system available for use. Testing these procedures to achieve an installed software system that may be used is known as installation testing.

When we test a release, you may need to roll back, this is often performed during the delivery lifecycle to ensure that Developers who release their code are able to back out their code using a simple process.

With the increase of CI/CD, this process is usually built into the development pipeline solution and tested as part of the management of these tools. An installation however is a little different, this is usually when you are testing an installation of a solution and ensuring that it can be uninstalled without leaving any residual files.

Logically, it’s fundamental that you make sure that users do not have any trouble when installing your software. If your software’s installation is successful, your customer will be satisfied, but if the installation fails, not only will the software not work on that system, but it could have damaged the user’s system. Of course, this is not a desirable position to be in.

Installation testing has become more complex with time, this owing to the many different ways software can be distributed nowadays. Whereas in the past software was distributed in the physical format of disks, nowadays it is commonplace for software to be installed from the internet, a network location or pushed to the user’s machine.

Upgradability Testing

Ensuring that a solution can be upgraded to a later version once in a productive state. Often when a solution or package is implemented (excluding SaaS or PaaS), it often needs to have regular upgrades to maintain the functionality, performance or security of the solution.

This testing ensures that you can upgrade the solution once it has been released into production. This will identify what type of outage would be required, providing confidence that the upgrade can occur in production within an outage window, reducing the impact on the business.

Back-up and Restore Testing

With the move to cloud and cloud services being reasonably stable, we are seeing this type of testing being shifted to the cloud hosting provider however it is essential that organisations have tested this to ensure business continuity.

Simple backups should be tested frequently, at least one a quarter and whenever this is a major hardware or software change to your backup system. It is important to run a test after upgrading your firmware in your backup system to ensure that the new firmware works as expected.

Often performed as part of the Disaster Recovery testing, this testing provides you with the confidence that you have your system and data restored in the event of a failure.

Failover and Fallback Testing

Often coupled within the Disaster Recovery testing, failover and recovery is essential more so given the level of complex integrations that organisations have.

Failover in computing terms is when the solution switches to a redundant or standby server, system, hardware component or network if there is a failure or abnormal termination on the active server, system, hardware or network. Failover is an automated process an operates without warning.

Failback is the process of restoring the server, system, hardware or network back to it’s original working state.

Disaster Recovery Testing

The purpose of Disaster Recovery (DR) testing is to assure that information technology systems can be restored if an actual disaster occurs. As part of a DR plan, companies typically engage a disaster recovery team, whether this is internally or specialists to recover the systems.  Effective disaster recovery testing can reduce downtime and save your organisation time and money if an actual disaster is experienced. There are a number of various methods that can be applied for a DR Test:

  • Paper test: This is where the test plan is read, and recovery plans are reviewed
  • Walkthrough test: A group of people come together and walk through the plans to identify issues and identify changes that may be needed.
  • Simulation: A group of people come together and walk through business scenarios to better understand whether the plan caters for these various situations. This is ensuring that emergency response plans, call trees are up to date and adequate.
  • Parallel test: Recovery systems are established and tested to see if they can perform business transactions to support key processes. Primary systems still carry the full production workload.
  • Cutover test: Recovery systems are established to assume the full production workload. All primary systems are disconnected.

Some simple steps can be followed to identify any errors during individual tests ad correct those before you do comprehensive tests. This saves time and the costs associated to errors interrupting a comprehensive test that engages a lot of people.

  1. Understand how frequently you should perform each type of test
  2. Test individual components – ensuring that the component can restore
  3. Perform wider tests including multiple components – ensuring that restoration at a point in time is possible and any interfaces can recover without loss of data
  4. Test the entire DR Plan, including all call trees and manual activities
operational acceptence testing be prepared
What we do

Whether you are following a traditional or Agile delivery model, we work with your business continuity and IT engineering team to ensure that the operational testing types are built into your delivery model, ensuring a safe landing into production.

We work with the business to understand the Business Continuity Plan, undertake a Business Impact Assessment and a Technical Impact Assessment – this helps inform the Operational Acceptance Testing that is needed to be performed prior to go-live.

How we can help

Accuteque recognises that the experience and skills of our team are what will drive quality and value from this engagement to you, the client. Accuteque has an exceptionally talented team with extensive, relevant experience in Operational Acceptance Testing to provide you the comfort that the business is able to operate when the new system is released.

We offer three core services:

  • Business Continuity Planning
  • OAT Strategy
  • OAT Testing

To learn more about our services and how we can help you.

Cybersecurity Partnership

Cybersecurity Partnership with SecurEyes Technical expertise with industry insight Cybersecurity Partnership with SecurEyes Technical expertise with industry insightCybersecurity partnershipBuilding a secure futureAccuteque is proud to announce a strategic...

Learning: Many heads are better than one

Many heads learn better than one Learning better togetherLast week, I had two very powerful experiences in the theme of learning. The first one was at work. At Accuteque, we are encouraging our team to engage in the space of Cyber Security, and many in the team have...

The Power of Metaphors

The Power of Metaphors Navigating Life through Diverse ImageryThe metaphors that govern our understanding of the world are not merely linguistic ornaments or poetic embellishments; they are fundamental tools for the human mind to understand and conceptualize complex...

Innovate for Equity

Innovate for Equity Bringing diversity into cybersecurity to protect everyone.In the month of February, I was part of a few events that were cybersecurity related. The first was a panel about "Women in Security", hosted at Splunk. Another was my own talk at "Test...


International Women's Day Hear about our team's experiences and passions to engage in a world of equality through championing equity. As a female founded and female led IT consultancy in a mainly male dominated industry Accuteque celebrate the achievements of women...

The home office – a new way of working

The Home Office - a new way of working Hear about what our team has done to thrive while working from homeA New Beginning Once upon a time, starting a new job and working from home did not go hand in hand. Now it is the norm, the new way of life after the last 2 years...

The office environment – a new way of working

The Office - a new way of working Hear about what our team has done to enjoy hybrid workingBeing in the office againThis is part 2 of our new ways of working blog, what happens when we return back into the office after a long time away? Some of our team have returned...

Working IN and ON the Business

Working IN and ON the Business What does a day in the life of a consultant look like?As a Quality Assurance Practice Lead my role requires me to work ON and IN the business. What’s the difference and why is it important to drive both? Working ON the Business  When we...

Multitasking by wearing many hats

The woman of many hats Multitaskers, many roles and switching in betweenWearing many hats at home and at work can mean a variety of things - being skilled in many different areas, having input in decisions, getting exposed to new ideas and ways of thinking, being...

Accuteque Principles Reflections

Reflecting on Accuteque's Principles We reflect on the importance of our Accuteque values and where they can be found in the everyday with the help of our Tangram.About Accuteque principles Accuteque principles are derived from focusing on both results and the...