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

Test plans

A test plan groups the test runs for a round of testing and tracks their combined progress. A one-time plan covers a single round between two dates. A recurring plan holds run templates and starts a fresh set of runs from them each time you start a cycle.

PropertyOne-time planRecurring plan
Created fromCreate > One-time planCreate > Recurring plan
HoldsManual one-time test runs, active or closedRun templates, manual or automated
ScheduleStart and end datesA Cycle Duration. Each cycle gets its own dates
Ends whenYou mark it complete, once every run is closedIt doesn’t end. You complete one cycle at a time, and archive the plan to stop it

You choose the type when you create the plan. It can’t be changed later.

Open Test Plans in the left navigation. The Plans page has two tabs, One-time and Recurring.

  • One-time: each row shows the plan’s runs, schedule, progress, and pass rate. You can filter by Status (Active or Completed), Created at, Start date, End date, and Completed by (the team member who completed the plan).
  • Recurring: each row shows the plan’s runs, active cycles, and cycle duration, with a New Cycle button. You can filter by Created at, Cycle Duration, and Archived.

To find a plan by name, enter it in Search plans, or press ⌘+F. To reorder the list, click Sort. On the One-time tab you can sort by creation date, name, end date, or progress. On the Recurring tab you can sort by creation date or name.

To manage the run configurations that plans and runs share, click Run configurations. See Run configurations. To manage mobile apps and their builds, click Apps. It opens the Apps tab of Test Assets. See Apps.

  1. On the Plans page, click the arrow next to Create and select One-time plan.

    The Create menu on the Plans page with One-time plan outlined, above Recurring plan, each with its description.

  2. Enter a title. It starts as “Test Plan - ” followed by today’s date. A description is optional. Usage Type is set to One-time. You can still switch it to Recurring before you save.

  3. (Optional) Click Link Runs, tick the runs to include, and click Link {n} runs. The list shows one-time manual runs only, active or closed. To find a run, search for it. To create a run instead, click New Run. Arcus asks you to save the plan first. Click Save & Continue, and a new test run opens. Set the plan in its Attach Test Plan field.

  4. (Optional) In Schedule, set the start and end dates. They default to today and 7 days from today.

  5. (Optional) In Notifications, enter email addresses separated by commas. Arcus emails them on start, on completion, and on failures. To post to Slack or Teams as well, click One Click to integrate. Once Slack or Teams is connected, pick a channel for each in Select Channel.

  6. (Optional) In Labels, click + and select or create labels.

  7. Click Create Test Plan, or press ⌘+↵.

    The New plan page with 3 runs linked in the Runs table, the Test Plan Properties panel with Usage Type, Schedule, Notifications, and Labels, and Create Test Plan outlined.

Arcus shows “Test plan created” and opens the plan. You can also link runs after you create the plan.

The plan page shows three cards above its runs:

  • EXECUTION SUMMARY: the pass rate, the number of test cases, and how many cases have each status across every run in the plan.
  • PROGRESS BY DAY: a bar for each day since the plan started, showing how much of the plan was complete that day. Hover over a bar to see the date and percentage.
  • PLAN LIFECYCLE: how many runs are still open.

A one-time plan page with the EXECUTION SUMMARY, PROGRESS BY DAY, and PLAN LIFECYCLE cards, one active run, a linked Testsigma plan in the properties panel, and Mark as Complete outlined.

The runs are split between Active Runs and Closed Runs. Each run’s ellipsis icon (⋯) offers the same actions as on the Test Runs page. To record results, open a run. See Execute a test run.

To add runs, open the plan, click Link Runs, tick the runs, and click Link {n} runs. You can also add a run from the run itself, with Add to Plan or Attach Test Plan. See Add a test run to a plan.

To create a run for the plan, click Link Runs > New Run. The new test run opens with the plan set in Attach Test Plan. See Create a test run.

A Match a filter run keeps gaining matching cases while it’s open, including inside a plan.

To remove a run, edit the run and clear its Attach Test Plan field. Each run can be linked to only one one-time plan.

  1. Close every run in the plan. Mark as Complete stays unavailable while any run is open, and PLAN LIFECYCLE shows how many are left.

  2. Click Mark as Complete.

  3. In the Mark this plan as complete? dialog, click Mark complete.

    The Mark this plan as complete? dialog over a one-time plan whose runs are all closed, with Mark complete outlined.

Arcus shows “Test plan marked as complete”. PLAN LIFECYCLE shows Complete, the schedule shows Closed, and you can no longer edit the plan, link runs, or link a Testsigma plan. The plan moves to the Completed filter.

Closing the last run doesn’t complete the plan by itself. Mark as Complete becomes available, and the plan stays active until you click it and confirm.

Link a one-time plan to an automated test plan in Testsigma, so you can start the Testsigma plan from Arcus and get its results back.

Before you link, set these up in order:

  1. Connect Testsigma to Arcus in Settings.

  2. Link the test cases between Testsigma and Arcus.

  3. In Testsigma, create a test suite with those cases and a test plan that runs it.

  4. In Arcus, create the one-time plan.

  1. Open the plan and, under Testsigma Automated Test Plan, click Link a Test Plan.

  2. In the Link Testsigma Automated Test Plan dialog, select the Project, then the Application, the Version, and the Test Plan.

  3. Click Link.

Arcus shows “Testsigma Automated Test Plan linked successfully”. The linked plan appears with its ID and name, and the plan’s description records the link. To start the Testsigma plan, click the Trigger Execution icon next to it. When the execution finishes in Testsigma, Arcus updates the linked test cases to Passed or Failed, with details from the execution. To unlink the Testsigma plan, click ×.

The Link Testsigma Automated Test Plan dialog with Project, Application, Version, and Test Plan selected, and Link outlined.

  1. On the Plans page, click the arrow next to Create and select Recurring plan.

  2. Enter a title. A description is optional.

  3. (Optional) Click Link Templates, tick the run templates to include, and click Link {n} templates. The list shows each template’s execution type and number of cases. To make a new template, click New Template. When you start from a saved plan, the new template opens with the plan set in Attach Test Plan.

  4. In Cycle Duration, select 1 Day, 1 Week, 2 Weeks, 3 Weeks, or 1 Month. It defaults to 1 Week.

  5. If you linked an automated template, set the Automation Settings. See Use automated templates.

  6. (Optional) Set Notifications and Labels, as for a one-time plan.

  7. Click Create Test Plan, or press ⌘+↵.

    The New recurring plan page with 2 templates linked, Cycle Duration in Test Plan Properties, and Create Test Plan outlined.

Arcus shows “Test plan created” and opens the plan. Nothing runs until you start the first cycle.

The plan page shows CYCLE HISTORY, a bar of test case results for each cycle with its pass rate, then CYCLES with Active and Closed tabs, then RUN TEMPLATES. The CYCLES table shows each cycle’s date range, state, and pass rate.

A recurring plan page with CYCLE HISTORY for 2 cycles, the CYCLES table, 2 run templates with run configurations, Automation Settings in the properties panel, and New Cycle outlined.

Click New Cycle in the plan’s header, or next to the plan on the Recurring tab. Arcus clones every linked template into a test run, shows “Cycle started. You’ll find it in this plan’s cycles.”, and opens the cycle. Each run is named after the plan, the template, and the cycle.

Each cycle lasts the plan’s Cycle Duration. You don’t have to wait for one cycle to end before you start the next, and you can start a cycle at any time. If an earlier cycle is still scheduled, the new cycle’s dates begin when that cycle ends, and its runs show Yet to start. You can still execute them right away.

New Cycle is unavailable when the plan has no templates linked.

The cycle page shows its dates and duration, then three cards: OVERALL, MANUAL, and AUTOMATED, each with its pass rate and number of cases. Cycle Settings on the right shows the cycle’s schedule and, if it has automated runs, its Automation Settings.

A cycle is frozen once it starts. You can’t add, remove, or delete its runs, and each run keeps the test cases and run configuration it was cloned with. To record results, open each run and set the case statuses. To switch between cycles, use the Cycle list next to the plan’s name in the breadcrumb.

In a cycle run, Edit Test Run changes only Assign Run and Labels. The schedule comes from the cycle, and the run configuration from the template.

A cycle page with the cycle dates and duration, the OVERALL, MANUAL, and AUTOMATED cards, 2 runs marked Yet to start, the Cycle Settings panel, and Mark Cycle Complete outlined.

To complete a cycle:

  1. Close every run in the cycle. Mark Cycle Complete stays unavailable while any run is open.

  2. Click Mark Cycle Complete.

  3. In the Mark this cycle complete? dialog, click Mark complete.

Arcus shows “Cycle marked as complete”. The cycle’s results become final and it moves to the Closed tab under CYCLES. The plan keeps running, so you can start the next cycle.

To add templates, click Link Templates on the plan page, tick the templates, and click Link {n} templates.

To remove a template, click the ellipsis icon (⋯) next to it under RUN TEMPLATES, click Remove from Plan, and click Remove in the Remove from this plan? dialog. Arcus shows “Removed from the plan”. The template itself isn’t deleted, and runs already created from it are kept.

Template changes apply from the next cycle. The current cycle keeps its runs.

Every automated run template in a recurring plan needs a run configuration before a cycle can start. If one doesn’t have it, the plan page shows a “Cycle not started” banner that names the template, and New Cycle shows “The action could not be completed”. To fix it, click Add configuration next to the template under RUN TEMPLATES and tick a configuration.

When a recurring plan has an automated template, its properties include Automation Settings. While you create the plan, set them in Test Plan Properties before you click Create Test Plan:

  • Environment: the environment the cycle’s runs read their variables from, such as Staging (default). See Environments.
  • Screenshot Capture: On, On failure (the default), or Off.
  • Screenshot Mode: Full page (the default) or Viewport.
  • Page Timeout (≤120s): in seconds, up to 120. The default is 30.
  • Step Timeout (≤120s): in seconds, up to 120. The default is 30.

Automation Settings in Test Plan Properties, with Screenshot Capture set to On failure, Screenshot Mode set to Full page, and both timeouts set to 30.

On the plan page, Test plan properties shows the values you chose.

Archive a recurring plan to stop it from producing cycles without deleting it.

  1. Open the plan and click the ellipsis icon (⋯) in its header.

  2. Click Archive Plan.

  3. In the Archive this recurring plan? dialog, click Archive.

Arcus shows “Recurring plan archived”. The plan is unlinked from its run templates and hidden from the Recurring tab. Cycles it produced keep their results, and a running cycle stays active. On an archived plan, New Cycle is unavailable.

To restore it, on the Recurring tab click Filter by > Archived > Archived only, click the ellipsis icon (⋯) next to the plan, and click Restore Plan. Arcus shows a reminder that its templates were unlinked. Link them again before you start the next cycle.

  1. On the Plans page, click the ellipsis icon (⋯) next to the plan and click Edit Plan, or Edit Recurring Plan for a recurring plan. You can also open the plan and click the pencil icon.

  2. Change the title, description, linked runs or templates, schedule or Cycle Duration, notifications, or labels.

  3. Click Save Test Plan, or press ⌘+↵.

Arcus shows “Plan updated”. You can’t change a plan’s type after creating it, or edit a one-time plan after marking it complete. A new Cycle Duration applies from the next cycle.

A public link lets people without an Arcus account see the plan’s progress. They see the summary cards, the runs, and the plan’s properties, and they can open each run’s own read-only page. They can’t change anything.

  1. Open the plan and click the share icon in its header.

  2. In Share Test Plan, turn on Anyone with the link can view. Arcus shows the link.

  3. Click Copy.

To stop sharing, turn off Anyone with the link can view. The link then shows “Invalid token”. If you turn sharing on again, the same link works again.

  1. On the Plans page, click the ellipsis icon (⋯) next to the plan and click Delete Plan. You can also open the plan, click the ellipsis icon (⋯) in its header, and click Delete Plan.

  2. In the Delete this plan? dialog, or Delete this recurring plan? for a recurring plan, click Delete.

What happens to the runs depends on the plan type:

  • One-time plan: its test runs aren’t deleted. They’re kept as standalone runs.
  • Recurring plan: its cycles and every run they produced are deleted permanently. Its run templates are kept.

Was this page helpful?