A workstation running terminal emulator sessions

    Legacy & virtualised apps

    Citrix is a video stream. That is fine — so is a person's eyesight.

    Published desktops, terminal emulators and vendor clients defeat every tool that binds to an object model. They do not defeat one that reads the screen.

    Proof

    Large International Bank

    85% of Citrix testing automated.

    A large bank automates Citrix application testing.

    Read the case study

    How is it done today?

    Today

    UAT stays manual, or an RPA licence binds to object IDs and breaks at the next vendor release.

    What does the agent do instead?

    How it works

    The agent does
    what the person does.

    Published desktops, terminal emulators and vendor clients defeat every tool that binds to an object model. They do not defeat one that reads the screen.

    Step 1

    Point the agent at the published window.

    It does not need to know whether the pixels came from a local process or a remote session.

    Step 2

    Describe the workflow in plain language.

    The instruction survives a vendor UI change that would have broken a selector.

    Step 3

    Schedule it or run it from CI.

    Coverage on a system that previously had none.

    What does a run leave behind?

    The output

    What a run leaves.

    Where it's the wrong tool

    • A slow remote session makes for a slow run — this inherits the latency of the desktop
    • Where the application has a documented API, use it
    • Regression coverage on applications nothing else can reach
    • A step report suitable for internal audit
    • No dependency on the application vendor

    Specs

    Who it's for
    Automation centres of excellence inside large IT organisations
    At a glance
    Works over Citrix · No object IDs · No vendor cooperation needed

    Send us ten test cases.
    We'll run them on your system.

    Or download AskUI Desktop. No sign-up.