# Quickstart

> Generate a test case with AI, automate it with Copilot, watch it pass, then add context from your tracker, coding agent, and pull requests.

Generate a test case from one sentence, let Copilot automate it in a cloud browser, and see it pass. You don't need an integration or anything installed. It takes about 10 minutes.

## Create a project

1. Click your project name at the top of the sidebar, then click **New Project**.

   ![The project switcher open. Callouts mark (1) the project name and (2) New Project.](https://s3.amazonaws.com/static-docs.testsigma.com/arcus/getting-started/quickstart_new_project.webp)

2. Enter a name and click **Create Project**.

Arcus fills in the project key from the name and opens the project's **Dashboard**.

## Describe what to test

1. On the **Dashboard**, under **AI Powered Test Case Generation**, click **Start Generating**. **QI Home** opens.

   ![The Dashboard's AI Powered Test Case Generation card outlined, with Start Generating.](https://s3.amazonaws.com/static-docs.testsigma.com/arcus/getting-started/quickstart_start_generating.webp)

2. In **What would you like to test?**, describe a flow in your web app, and include the app's URL.
3. Click **Send**.

![QI Home with a prompt in What would you like to test?. Callouts mark (1) the prompt, with the app's URL, and (2) Send.](https://s3.amazonaws.com/static-docs.testsigma.com/arcus/getting-started/quickstart_describe_what_to_test.webp)

## Generate the test cases

The Test Authoring Agent reads your prompt and asks how to start.

1. Choose **Continue with test case generation**. It writes test cases straight away, without crawling the app first.
2. When the **Generation Plan** appears, click **Approve**.
3. When the agent lists the scenarios it outlined, click **Yes, proceed with all**.

The test cases appear in the session's review list, marked **Pending**.

## Automate and run a test case with Copilot

1. Open one of the test cases.
2. Click **Learn with Copilot**.
3. Under **Where to run**, select **Cloud**.

   ![Copilot configuration with Cloud selected and outlined under Where to run.](https://s3.amazonaws.com/static-docs.testsigma.com/arcus/getting-started/quickstart_where_to_run.webp)

4. Click **Start Copilot**. The session opens in a new tab, and the cloud browser can take a minute to start. If your browser blocks the new tab, the session opens in the current one.

   ![The Start Copilot button outlined at the bottom of Copilot configuration.](https://s3.amazonaws.com/static-docs.testsigma.com/arcus/getting-started/quickstart_start_copilot.webp)

5. Click **Start learning**. Copilot drives the browser through each step and shows what it did, until it shows **Learning complete**.
6. Click **Save and Run**.

Arcus saves the test case to your library with an ID, marks it **Accepted**, and runs the automated steps straight away.

## Check the result

Each step shows a tick as it passes, and the session shows **Paused at the end of the test** when the run finishes.

To see the run again, open the test case, select **Run history**, and click the run. See [Run results](https://testsigma.com/docs/arcus/v2/results/run-results/).

![A test case's Run history tab. Callouts mark (1) Run history and (2) a passed Copilot run.](https://s3.amazonaws.com/static-docs.testsigma.com/arcus/getting-started/quickstart_run_history.webp)

## Add your own context

The test case you just ran came from one sentence. Arcus writes more specific test cases when it can read your real work: your stories, your designs, and what your developers change. There are 3 ways to give it that context.

- **In the prompt**: below the prompt box in QI Home, click **Jira Requirements**, or **+** for the other sources. You can attach Azure DevOps, Linear, ClickUp, or OpenProject work items, Confluence pages, and Figma designs. You can also attach pull requests from GitHub, GitLab, or Bitbucket, files (.jpeg, .png, .docx, .pdf, .xls), and video recordings (.mp4, .mov, .webm, .avi, .mkv). Each upload can be up to 500 MB. A source you haven't connected shows **Integrate**, which opens **Settings** > **Integrations**. See [Add context](https://testsigma.com/docs/arcus/v2/qi-home/context-management/).

  ![The Add Context dialog with the list of context sources outlined: Jira, Azure DevOps, Linear, ClickUp, OpenProject, Confluence, Figma, GitHub, Bitbucket, GitLab, Files and Documents, and Video Recording.](https://s3.amazonaws.com/static-docs.testsigma.com/arcus/getting-started/quickstart_add_context_sources.webp)

- **From your coding agent**: install the Arcus plugin in Claude Code, Cursor, Codex, or GitHub Copilot. It captures each coding session, including prompts, tool calls, and file changes, and sends it to **Context Management** in QI Home. Setup is the same in every tool: install the plugin, sign in with `/arcus:login`, and set the project with `/arcus:project use`. The plugin sends nothing until you sign in. To file a session under a sprint, link its ticket with `/arcus:map ticket`. In Cursor, the commands use a hyphen instead of a colon, as in `/arcus-login`. To start, click **Connect code tools** at the bottom of QI Home, or see [Developers](https://testsigma.com/docs/arcus/v2/qi-home/developer-tools/plugins/).
- **From pull requests**: connect GitHub with the Arcus GitHub App, or connect GitLab or Bitbucket. Every pull request your team raises reaches Context Management. When its title or description carries a ticket ID from your tracker, Arcus maps it to that ticket's sprint automatically. See [GitHub](https://testsigma.com/docs/arcus/v2/integrations/plugins/github/).

To check what's connected, click the more options icon (⋯) on QI Home, then **Manage integrations**. Connected coding tools show **Active** under **Dev Tools and AI**.

![The QI Home more options menu. Callouts mark (1) the more options icon and (2) Manage integrations.](https://s3.amazonaws.com/static-docs.testsigma.com/arcus/getting-started/quickstart_manage_integrations.webp)

## What's next

- **Test your own app**: pick your app type ([web](https://testsigma.com/docs/arcus/v2/apps/web/create-test-cases/), [mobile](https://testsigma.com/docs/arcus/v2/apps/mobile/create-test-cases/), [desktop](https://testsigma.com/docs/arcus/v2/apps/desktop/create-test-cases/), [API](https://testsigma.com/docs/arcus/v2/apps/api/api-tests/), or [Salesforce](https://testsigma.com/docs/arcus/v2/apps/salesforce/create-test-cases/)), and install the [Arcus Agent](https://testsigma.com/docs/arcus/v2/get-started/installation/arcus-agent/) to test on your own machine.
- **Bring your team**: invite teammates, and turn on **Review Management** so test cases are approved before they're used.

  ![Project Settings > Overview with the Review Management toggle outlined.](https://s3.amazonaws.com/static-docs.testsigma.com/arcus/getting-started/quickstart_review_management.webp)

- **Map your app first**: let the Explorer Agent crawl your app before it writes test cases. See [App knowledge graph](https://testsigma.com/docs/arcus/v2/qi-home/app-knowledge-graph/).

## Troubleshooting

### The agent doesn't reply after I send the prompt

Wait 2 minutes, then go back to **QI Home** and send the prompt again in a new session. Check that the URL in your prompt is complete and opens in a browser.

### Start learning doesn't respond

Click **Start learning** once and wait. If nothing happens after a minute, end the session with the exit icon at the top of the session, then **End session**. Start again from **Learn with Copilot** in the test case header, with **Where to run** set to **My local machine**. This needs the [Arcus Agent](https://testsigma.com/docs/arcus/v2/get-started/installation/arcus-agent/) running on your computer.

### A step fails during the run

Copilot learned from the live app, so a changed page can break a step. Click **Re-run**. If the same step fails, see [Debug and run with Copilot](https://testsigma.com/docs/arcus/v2/automation/copilot/).
