Within the solution Steer73 was building, there was a collection of physical scanning devices. The devices were large and very expensive, making obtaining a test machine impractical. Furthermore, COVID restrictions meant that the development team was unable to attend site.
This meant that:
- Steer73 had no conventional means of testing their solution against the integration as they built it
- Risk was skewed towards the end of the project when code could be tested on the real hardware
- There was a large unknown at the end of the project, leading to uncertain timelines and costs
Determined to deliver a robust solution, on time and on budget, Steer73 tackled the problem by building a series of virtual test rigs.
By working extremely closely with the hardware provider and all stakeholders, Steer73 was able to create mock instances of the external integrations.
Including a ‘virtual hardware’ mode in the application allowed the team to simulate specific hardware events. A simple scripting language extended this further, allowing the team to replay a large number of events sequentially. This included simulated delays, representing real-world usage.
This approach enabled both a wide range of different tests to be performed and also an incredible volume of test runs to be done.