ecu.test now  supports an entirely new workflow: Develop test cases locally and run them on a matching HiL or SiL test bench in just a few clicks via remote scheduling – without locking the test resource and without waiting for results. Our video shows how this works in practice.

Creating and commissioning new test cases only works with direct control and immediate feedback from the test bench. But test resources are rare and in high demand – whether HiL or SiL.

On top of that, there used to be another catch: When several teams shared a test bench or test resource, one person's running configuration locked access for everyone else. Even when no test was running at all. That made test case development both slow and inefficient.

 Here's what changes now:

1. With the new Offline mode, you can start a configuration without occupying the test resource. Test cases can be created and edited without a direct connection to the test bench environment – and the test bench stays available for everyone else, including CI automation.
2. Once a test case is ready to run, the new Remote scheduling takes over. The new execution mode in ecu.test schedules the test case on a matching test bench. From there, test.guide/one:cx handles the rest: The test is queued and executed as soon as the selected test resource becomes available.

Because execution runs in the background in test.guide/one:cx, you can keep working in ecu.test – on your next test case, for example. As soon as the results are ready to review, you'll get a notification in ecu.test.

What this means in practice

No more waiting for a free test resource. Multiple users can develop and schedule tests at the same time without blocking each other. And test resources are only in use when tests are actually running.

Questions about your setup, or not using test.guide/one:cx yet? Get in touch with us.