Eight examples from everyday use in business departments — as a starting point to adapt to your own Windows application, not as a rigid template. Get started with Getting Started, then fine-tune your setup under Tips & Tricks.
Instead of typing every incoming order into the same screens by hand, Automation Studio replays the test case that was previously recorded via mouse and keyboard — as often as needed, with nobody sitting there watching. The result is a purely step-based pass/fail verdict — no room for interpretation.
After an update to the target application, buttons and input fields often no longer sit exactly where they were when a test case was recorded. Because Automation Studio locates click targets through an image anchor rather than fixed coordinates, and allows an adjustable tolerance, the automated flow keeps running unchanged — no re-recording required. That holds just as well for your own business application as for software teams checking after every release that the test case still passes.
Anyone entering a hundred similar records by hand eventually loses focus — Automation Studio doesn't. With a defined repeat count of 1 to 999, it replays the same test case automatically over and over and continuously shows progress — if one particular run fails, that exact run can be traced in the report instead of throwing the whole batch into doubt.
Once several customers or departments each need their own recurring flows automated, organizing test cases into folders keeps things manageable. Each customer or department gets its own area, so test cases don't overwrite each other or disappear into one long list.
Because every test run is stored in the run history with its metadata, two runs can be compared directly — for example the last run before a price list change in the ERP and the first one after it. That makes it immediately clear which step changed, instead of relying on the impression that things "seem to match now."
Instead of letting the remaining steps run against an already inconsistent state after a failure, the "Stop on error" option halts playback immediately. The target application stays exactly in the state where the failure occurred — ideal for tracing the root cause right on the spot.
An existing set of test cases can be exported as a file and imported again on another machine. New colleagues don't need to record anything from scratch — they inherit the already proven flows directly, and can adapt them to their own environment afterwards if needed.
After every test run, Automation Studio automatically generates an HTML report listing all steps, their result, and diff images at the relevant points. That single file opens without any extra software and can be forwarded directly to a customer or business department — solid evidence that a flow was carried out.