Even while the fake scans are running, users can explore other pages, delete/repeat steps, check images, change settings. For that I established a readable, maintainable Angular-based SPA, that allows building robust prototypes. These allow users to explore a large bandwidth of functionalities, without breaking so easily.

Users sometimes want to adjust settings mid-scenario. To make this possible, I implemented a “fake memory” logic in the prototype. This temporarily stores settings that directly affect the UI and can be discarded if needed → effectively simulating memory in a test environment.

The test scenario on the left is configured with specific “Spine” settings to provide the appropriate steps and images, all within the same app shown in earlier examples. How? I integrated dynamic inputs into the testing frontend, enabling precise adjustments for tests — such as examination speed, image sets, or even introducing sudden errors at specific steps.