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

Projects and project settings

A project holds the test cases, step groups, test runs, plans, and test assets for one application or initiative. The pages in the left navigation, from QI Home to Reports, show the project selected in the project switcher at the top of the navigation. The same switcher opens Project Settings and creates new projects.

The project switcher open, with Project Settings and New Project outlined.

  1. Open the project switcher at the top of the left navigation and click New Project. The Create a New Project page opens.

  2. In What would you like to name your Project?, enter the project name.

  3. (Optional) Enter a Description.

  4. Check the Project Key. Arcus fills it in from the name. The key starts the ID of everything in the project, followed by a number. To use a different key, type over it. The key is turned into capitals, can be up to 10 characters, and must not match another project’s key.

  5. (Optional) To read sprints from Jira from the start, click Link Jira Project. You can link it later from Project Settings.

  6. Click Create Project.

The Create a New Project page, with Project Key and Link Jira Project outlined.

Arcus switches to the new project and opens its Dashboard.

Open the project switcher and click Project Settings. The page has 4 sections: Overview, Import, Export, and Salesforce. To work on another project, pick it from the project list at the top right of the page.

Project Settings > Overview, with the section list, Link Jira Project, and the Review Management and Copilot Visual learning toggles outlined.

Overview holds the project’s details and settings:

  • Project Name and Description: click the edit icon beside either one to change it.
  • Project Key: read-only. You can’t change the key after the project is created.
  • Project Management Tool: click Link Jira Project to choose the Jira project Arcus reads sprints and stories from. Other trackers link from QI Home. See Generate for a sprint.
  • Testsigma Project: click Link Testsigma Project to connect a project in the Testsigma automation platform.
  • Review Management: turn it on to have test cases reviewed and approved before they’re ready. See Review test cases.
  • Copilot Visual learning: turn it off to stop Copilot keeping a screenshot of the app with each step. Use this for sensitive projects. Password fields are always masked.

The delete icon at the top right of Overview deletes the project with all its test cases, runs, and plans. In the Delete Project dialog, select Confirm deletion; this action is permanent and cannot be undone., then click Delete Project. The demo project can’t be deleted.

Test properties are the 4 classifications every test case carries. Each has a set of values, which you rename or extend here.

  • Test Case Priority: the urgency and execution order of a test case. It starts with Critical, Major, Medium, and Minor.
  • Automation Type: the automation state of a test case. It starts with Automated, Manual, Not Automated, In Progress, Automation Not Required, and Obsolete.
  • Test Case Status: the current state of a test case in the testing lifecycle. It starts with Draft, Ready, Reviewed, Archived, In Review, Obsolete, and Rework.
  • Test Case Type: the category of a test case, based on its purpose and testing approach. It starts with Functional, Regression, Smoke, Performance, Integration, Manual, Unit Test, Non Functional, and User Experience.

Values your team adds, or that an import creates, are listed after these in Settings > Manage Properties, so your account may show more.

  1. In the left navigation, go to Settings > Manage Properties.

  2. Click Edit. The Edit Properties panel opens.

  3. Click the value you want to rename and edit it in place.

  4. Click Update Details.

  1. In the left navigation, go to Settings > Manage Properties.

  2. Click Edit.

  3. Click the plus icon (+) beside the property you’re adding to. A row opens with the placeholder Enter property name.

  4. Enter the name, then click the check icon to keep it. To drop the row instead, click the cross icon.

  5. Click Update Details.

A custom field adds project-specific information to a test case, beyond the default test properties. Once a field exists, you can set it on test cases and filter the list by its values.

  1. In the left navigation, go to Settings > Custom Fields.

  2. Click + Add New. The Add new field in Test Case panel opens.

  3. Enter a Field Name.

  4. (Optional) Enter a Description.

  5. Select the Field Type.

  6. If the field type offers choices, enter its options.

  7. Click Add. The field appears in the Custom Fields section.

A field takes 1 of 8 types:

  • Text field: a single line of text.
  • URL: a link.
  • Text area: several lines of text.
  • Date picker: a date.
  • Dropdown select: one option from a list you define.
  • Checkbox: a single on or off choice.
  • Radio Button: one option from a set you define.
  • Multi select: several options from a list you define.
  1. In the left navigation, open Test Cases, then create or open a test case.

  2. In the Test Properties section, select the custom field values.

  1. In the left navigation, open Test Cases, then select the test cases to update.

  2. Press Command+K and choose the custom field to edit.

  3. In the <Custom_Field_Name> dialog, select or enter the value to apply.

  4. Click Update <number> Test Cases.

  1. In the left navigation, open Test Cases.

  2. Click Filter by, or press Command+Shift+F.

  3. In the Filter by dialog, select the custom field to filter on. The list narrows to test cases matching your selection.

A label categorizes test cases and test runs so you can filter and track them. For example, label by functionality: Smoke Test, Regression, or API Testing.

  1. In the left navigation, go to Settings > Manage Labels.

  2. Click Edit.

  3. Click Add Labels.

  4. Enter a Name.

  5. Click the check icon to save.

  1. In the left navigation, go to Settings > Manage Labels.

  2. Click Edit.

  3. Select the label to update.

  4. Update the Name.

  5. Click Update Details.

  1. In the left navigation, go to Settings > Manage Labels.

  2. Click Edit.

  3. Click the delete icon next to the label.

  4. Confirm in the Delete <Label_Name> dialog.

Project Settings > Import brings test cases and step groups into the project. Its Test Cases and Step Groups tabs each list past imports with their results.

  • Test Cases: click Import via CSV for a spreadsheet, or Quick import from to copy a project from another test management tool with its history. See Import from CSV and Quick import.
  • Step Groups: click Import via CSV. See Import step groups.

Project Settings > Export saves the project’s test cases as an Excel (.xlsx) file.

  1. In Project Settings, open Export.

  2. Click Export. The Export test cases dialog opens with the number of test cases to export.

  3. Click Export (n).

To export only some test cases, filter the Test Cases list, then click the more options icon (⋯) and click Export. The same dialog opens with the list’s filters applied. See Import and export.

The file has three sheets: Test Cases, Test Steps, and Step Groups. Step Groups holds the step groups the exported test cases use. The dialog counts test cases only.

Arcus builds the file in the background. If you stay on the Export page, the file downloads when it’s ready. Every export is also listed on that page; click the download icon on an export to download it again. Arcus also emails you when the export is complete.

Project Settings > Salesforce connects the Salesforce orgs this project tests. Click Connect Salesforce to start. See Connect and sync an org.

Was this page helpful?