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

Datasets

A dataset is a table of test data that test cases share. Each column is a variable, and each row is one set of values. Attach a dataset to a test case to use its values in automated steps, or to run the same steps once for every row.

Datasets are on the Datasets tab of Test Assets. Some screens still call them Data Sets, for example Search Data Sets.

The Datasets tab of Test Assets, listing a dataset with its variables, rows, creator, and dates, with Create outlined

  1. In the left navigation, open Test Assets.

  2. On the Datasets tab, click Create.

  3. Enter a name for the dataset.

  4. (Optional) Describe what the dataset contains and what it’s for.

  5. Click Create Dataset.

    The Create a Dataset dialog with a name and description entered, and Create Dataset outlined

Arcus shows “Test Dataset Created” and opens the dataset with an empty Data Structure table of two columns and two rows. Its ID appears in the page address.

  1. Click a column header and type the variable name.
  2. Click a cell and type its value.
  3. Click outside the table to save the value. The time beside Last Saved updates.
  4. To add more, click Add Column or Add Row.

To change a column, click the ellipsis icon (⋯) in its header:

  • Column Type: Text (the default), Number, Boolean, Date, URL, or Email.
  • Add Column After and Remove Column.

A dataset table with a column menu open and Column Type outlined

The column type is shown under the column name in capitals wherever the dataset is attached. Arcus doesn’t check values against the type. A Date column accepts any text, so enter every date in the same format.

To add or remove a row, click the ellipsis icon (⋯) beside the row number, then click Add Row After or Remove Row.

To rename the dataset, click its name at the top of the page and type. The breadcrumb updates when the name saves.

  1. Open the test case.
  2. In the dataset line, click Create Dataset.
  3. Enter a name, and optionally a description, then click Create Dataset.
  4. Enter a variable name in each column header and the values beneath them. Click Add Column or Add Row for more.
  5. Click Link Dataset.

Arcus links the new dataset to the test case with all its rows.

  1. On the Datasets tab, click Add from CSV.
  2. Enter a Dataset Title. A description is optional.
  3. Drag a .csv file into Add Files, or click Select a File.
  4. Click Preview.
  5. Check the Dataset Preview and, under Add Info, the File Name, Columns Detected, and Total Rows.
  6. Click Add.

The first row of the file becomes the column names, and every column is a text column. Arcus creates the dataset and opens it.

The Datasets tab lists every dataset in the project with its number of VARIABLES and ROWS, who created it, and when it was created and last updated. Search with Search Data Sets.

Click the ellipsis icon (⋯) on a row for:

  • Clone: opens Clone Dataset, where you can change the name and description, then click Clone Dataset. The copy has all the variables and rows, and its name defaults to the original’s with “Clone” added. Changes to the copy don’t affect the original.
  • Delete: removes the dataset after you confirm.
  1. Open the test case and open the Automated steps tab.

  2. Below the steps, click Add Dataset. If the test case has no dataset yet, the link reads “No dataset(s) added. Create Dataset or Add Dataset”.

  3. Select the dataset, then click Next.

    The Add Dataset dialog with a dataset selected, outlined, and Next enabled

  4. Select the rows to use. Select the checkbox in the header to use every row.

    The Add Dataset dialog's row step, with the header checkbox and every row's checkbox selected, outlined

  5. Click Add Dataset.

Arcus shows “Dataset added” and adds the dataset under Dataset on the Automated steps tab, with each column’s name and type. The link is live: columns and values you change in Test Assets show on the test case straight away. To edit the data, click Manage Dataset in the Add Dataset dialog. It opens in a new tab.

The Automated steps tab with the attached dataset below the steps, and the column names with their types outlined

Repeat the attach steps to link a second dataset. Arcus combines the linked datasets by Cartesian product, generating one test scenario for every combination of rows. Two rows in one dataset and three in another give six scenarios.

  1. In the automated steps, click the value you want to replace.
  2. Open the Parameter tab.
  3. Select a column. It’s inserted as {row.<column>}.

The Parameter tab lists each attached dataset first, with the hint “click adds a For each over it”, then its columns.

A step's value picker with the Parameter tab open, and the attached dataset and its column values outlined

A dataset value is written {row.column}, for example {row.city}, and works only inside a For each loop over the dataset. Move a step that uses one into the loop’s body. To add a loop, see Repeat steps for each row.

If you leave out row., as in {city}, Arcus reports that the column is readable only through the binding of a loop over its dataset, and tells you to read it as {row.city}.

  1. Click the empty row at the end of the steps that reads “Type a step, or / for blocks”.
  2. Type /. The list of blocks opens.
  3. Select For each. A For each block appears with an empty body and the warning “empty for block”.
  4. Click the block. Step settings opens.
  5. Under over, select a dataset.
  6. Select the dataset. The hint below it lists the columns each row has.
  7. In the block’s body, add the steps to repeat. Use Parameter values, written as {row.<column>}, for the parts that change.

The block reads “For each row in” followed by the dataset’s name. The binding field sets the name each row is read through, row by default. The over field can also loop over the elements at a locator, or a number range.

When the test case runs, Copilot runs the block once per row. The body step shows the number of the pass it’s on. If one pass fails, the run stops there, and the error names the value that failed.

Attach it to each test case. Changes to the dataset show in every test case that uses it.

A For each step says the dataset isn’t one the test can iterate

Section titled “A For each step says the dataset isn’t one the test can iterate”

The dataset was renamed, or it isn’t attached to this test case. Attach it, then open the For each step’s settings and pick it again.

Keep values different between Staging and Production

Section titled “Keep values different between Staging and Production”

Use environment variables instead of a dataset. See Environments.

Was this page helpful?