We achieve that by enhancing the skills and capabilities of existing teams through:
Incubate mature digital service teams that can deliver predictably, adapt appropriately to emerging scope, and meet the needs of the organization and its constituents.
Automate the often manual testing of multi-step business processes across more than one system. Tests are built that simulate complex journeys to ensure software is behaving as expected. These automated tests enable additional testing services, such as automating data entry into legacy systems, realistic load testing, and integration testing.
Testing government digital services, like unemployment insurance, often requires realistic mock data to be in place before any testing activities can happen. Building, managing, and clearing mock data across multiple systems, including identity verification, wage/employment records, and authentication is a tedious and time-consuming process.
Automating the process of generating this data eliminates hours of manual effort required to create the large amount of mock data needed for a robust testing program.
Site Reliability Engineering (SRE) is the art of making an application as efficient, robust, and resilient to failure as possible. The objective is to improve the reliability of an application, and this is done by observing, replicating, and remediating issues that might otherwise take the service down.
This can take several forms, including:
Load testing simulates a digital service under various types of heavy load to identify performance issues and determine monitoring thresholds. This can take the form of basic HTTP request testing, scripted (“end-to-end”) testing, stress testing, breakpoint testing, and soak testing.
The above types of load testing are scripted ”end-to-end”. With this approach to load testing, traffic simulates real-world use cases through an application which often means crossing multiple endpoints. Therefore load is often applied to multiple endpoints at once, and can occasionally involve using an automated web browser for realism.
This provides an opportunity to validate how a service performs “in the real world”, such as during an initial launch. It provides ongoing safety when there’s uncertainty if technical change to a product will impact site reliability.