8. Be able to test the end-to-end service in an environment similar to that of the live version, including all common browsers and devices.

The purpose of this point is to make sure that the service can be tested in an environment that is a close replica of the live environment, not only during development but throughout the life of the service. This is particularly important where the service relies on integrations to other systems or data registers.

As services will be part of a continual improvement review, it is important to be able to test changes. This will also help with troubleshooting any issues that may occur in the live environment.

Infrastructure environments should be constructed in such a way as to allow for controlled development, unit testing and integration testing to take place ahead of service release and go-live.

In a self-service environment, where the end user devices will be many and varied, it is important that the service is tested on the devices and internet browsers that we know are in use within the user base. This will require some analysis of current user behaviour to determine the device and browser types in use. Where integrations to systems or data registers are included, data protection considerations should be given to the types of data that may be accessed from a test environment. Where required, a risk assessment should be undertaken.


The Standard was launched on 7 April 2016.

This guidance was last amended on 17 June 2016 as part of Service Standard Sprint #1.

You can read more about the Standard here.

All content in this guide is available under the Open Government Licence v3.0, except where otherwise stated.