Squirt 3.21
Usage

Squirt GUI tests follow the WinCC OA OaTest concept.

Typical workflow

  1. Record macros and verification points against native panels (.pnl / .xml).
  2. Replay tests locally (GEDI + HSP) or from the command line.
  3. Run the same suites under WinCC OA TestFramework in CI/CD.
  4. Review assertion logs and screenshots on failures.

Execution modes

Mode When to use
GEDI + HSP Interactive development and local debugging
Command line Repeatable local runs without the IDE UI
TestFramework / CI Automated gates and release validation

Shape addressing constraints

  • Do not use : in panel names.
  • Do not leave shape names empty.
  • Prefer unique shape names (especially inside Tab shapes).
  • Avoid randomly generated module, panel, or shape names.

Only WinCC OA shapes can be recorded and replayed (no file selectors, printers, and similar OS dialogs).

DPE monitor showcase

scripts/examples/splash/vision/dpe_monitor/DpeMonitorShowcase.ctl is a small hand-authored example of OaGuiTest: it toggles the comment-display checkbox, refreshes the empty table, restores the checkbox, and compares the stable FRAME1 shape with the stored VP at data/splash/VPs/dpe_monitor_showcase.json.

Run it with the DPE monitor panel available in the test project:

WCCOAui.exe -p "vision/dpe_monitor.pnl" -log "+stderr" -proj "<test-project>" -s "<Squirt-subproject>/scripts/examples/splash/vision/dpe_monitor/DpeMonitorShowcase.ctl"

The VP baseline is committed with Squirt and is resolved from the configured subproject; the showcase does not create or modify test-project data.

CLI tests

The suite_CLI test run exercises the path validation shared by sq-cli and the production CLI. It runs under a CTRL manager with -n, does not start a UI manager, and can run in a headless environment such as the current GitHub Actions image.

Run it locally through CtrlTF:

& '<WinCC OA installation>/bin/WCCOActrl.exe' -proj TfCustomizedSquirt testRunner.ctl cli -n -log +stderr

The test suite and its coverage are documented in suite_CLI.

The suite does not start or stop WCCOAui. Recording, pause/resume, stop, and replay integration checks require a working display and a test project with the panel available. Run those checks locally; they are excluded from headless CI until a display is available in the GH image.

Made with ❤️ for and by the WinCC OA community