Skip to content
Docs
Arcus
Popular questions
↑↓ to navigate↵ to selectesc to close
Book a demo

Learn with Copilot

Turn a test case’s manual steps into automated steps. Copilot reads each step and its expected result, drives your app through them in a live browser, and writes an automated step for each one.

  • The test case needs manual steps. If it has none, use Record and author instead.
  • To learn on your own machine, sign in to the Arcus Agent.
  • Start learning in one go. Clicking Learn with Copilot replaces the tab’s empty state with the step editor, even if you cancel.
  1. Open the test case and select Automated steps.

  2. Click Learn with Copilot.

    Learn with Copilot on a test case that has manual steps but no automated steps, outlined

  3. In the Copilot configuration, choose What you are authoring and Where to run. See Copilot configuration.

  4. Click Start Copilot.

The session opens in a new tab. If your browser blocks the new tab, it opens in the current one.

Copilot lists the steps it will learn from under Manual steps. The precondition and each expected result appear as separate items. On some accounts, an Engine list also appears for web and Android apps. It sets which learning engine Copilot uses: Legacy, the default, or Sherpa.

A learning session, with the Manual steps list, Engine, Start learning, Record and author, and the prompt box outlined

The prompt box below the chat takes instructions in your own words, up to 350 characters. Click Generate to send them.

  • Refine: rewrites your prompt with AI before you send it.
  • Auto or Manual: with Auto, Copilot keeps going and tells you what it assumed. With Manual, it stops and asks whenever a choice matters.
  • Type / for commands:
    • /manual-steps: shows the test case’s manual steps.
    • /relearn: learns the app again from the manual steps.
    • /intent-step: adds an intent step. It’s available only once the test case has automated steps.

The prompt box with the command list open, with the commands and Auto outlined

Click Start learning. To record the steps yourself instead, click Record and author. See Record and author.

The status line shows Arcus is learning, the step it’s on, and a timer.

For each step, Copilot shows a card with the step and its expected result. The card also shows what Copilot observed on the page, and the action it took, such as Navigate to, Click on, or Assert Text Visible. When a step matches more than one element, Copilot stops and asks you, if Pause on ambiguity is on in the configuration.

To stop Copilot while it works, click the stop button in the prompt box.

When it finishes, Copilot shows Learning complete, how many steps it learned, and a summary:

  • Manual steps you started with: the steps in the test case now.
  • Automated steps: the steps Copilot will write. Click Remove to leave a step out.
  • Updated manual steps: Copilot’s rewritten manual steps, which replace the ones the test case has now.

To compare the test case’s current steps with the learned ones, click What changed. Turn on Only differing steps to hide the steps that match.

Click Save and Run. The button changes to Saved, and the automated steps run straight away.

Saving also sets the test case’s Automation Type to Automated. To find the run later, open the test case and select Run history. See Run results.

Copilot learns from the app as it is during the session, so check these before you rely on the steps:

  • Dates: a relative date such as “7 days from today” becomes a fixed date.
  • Live values: a value that changes, such as a count of search results, is checked literally.
  • Ambiguous elements: a step can pass while learning and fail on replay. The error says “5 visible elements match this element, and the step needs exactly one.” Re-record the element against the one you mean. See Elements and locators.

To change a learned step, open the session with Debug with Copilot. See Debug and run with Copilot.

A test case that QI Home generated isn’t in your library until you accept it. In the session’s review list, open the test case and click Learn with Copilot. Save and Run then also saves the test case to your library with an ID and marks it Accepted.

Generated test cases offer Start learning only, not Record and author.

If nothing happens after a minute, end the session and start it again with Where to run set to My local machine.

Learn with Copilot is gone after a session that learned nothing

Section titled “Learn with Copilot is gone after a session that learned nothing”

The automated steps tab now shows the step editor. Click Learn with Copilot in the test case header to start learning again.

If Chrome for Testing doesn’t start, choose Chrome under Browser on this machine and start the session again.

Was this page helpful?