Products

Test Suites

Suites organize test cases, steps, hooks, schedules, data rows, and execution history for repeatable automation.

Suite Structure

A suite contains one or more cases. Each case contains ordered steps and optional row-based data. Suite-level hooks can prepare state before execution or clean up afterward.

Cases can be run individually, in batches, or as part of a suite run. When data rows are present, each row becomes a distinct execution unit in the batch tree.

Test Suite page with cases and execution sidebar
A test suite showing cases, step list, data table, and execution batch sidebar.
1

Open a project and choose a suite.

2

Add a case with a clear goal, such as Create Supplier or Validate Login.

3

Add steps through the Step Editor or AI generator.

4

Add test data rows if the same case should run with multiple inputs.

5

Run the case or suite and inspect the generated execution batch.

Working With Data Rows

Data rows let one case execute multiple times with different values. Use row-based data for employees, supervisory organizations, locations, compensation plans, or any repeated parameter set.

Practical Tips

  • Keep column names business-readable because they become easier to reference in prompts and step code.
  • Use a small smoke row set before scaling to large batches.
  • Separate destructive scenarios from read-only validation scenarios.

Hooks, Schedules, And Batch Runs

Suite-level hooks are useful for setup and cleanup that should run around cases. Schedules help teams run repeatable suites without manually launching each one. Batch runs keep every case and row grouped under one result tree.

1

Use a before hook to prepare shared state such as login or navigation.

2

Use an after hook to clean up temporary records when the workflow allows it.

3

Create schedules only after the suite is stable in manual runs.

4

When a scheduled run fails, inspect the first failed case and row before editing the whole suite.

Failure Review

Suite failures usually come from one of four places: bad row data, environment login issues, changed Workday UI state, or brittle step logic. The result tree, screenshots, videos, and action logs should point to the right layer.

Practical Tips

  • If every row fails at login, inspect the environment credentials.
  • If one row fails and others pass, inspect that row data first.
  • If failures begin after a Workday update, review selectors and visible labels in the failing step.