Test Cases
Test Cases are the core execution units in AutoBP, representing single operational or validation scenarios.
Test Case Anatomy & Tags
A Test Case represents a single automation scenario in AutoBP, such as "Validate Login" or "Create Supplier". Each case maintains an ordered list of Steps that perform the actions, and holds metadata including tags, concurrency limits, and custom configuration.
Click "Add Case" inside a Suite and give it a descriptive name.
Apply tags using the tags input box to group and categorize the scenario.
Use the selection checkboxes to filter and bulk-delete or bulk-run specific tagged cases.
Clone existing cases or convert them into reusable BP workflows when needed.
Practical Tips
- Keep test cases focused on a single business outcome to simplify failure diagnosis.
- Apply tags consistently across the suite so you can quickly filter for daily sanity checks or full regressions.
Case Hooks & Optimization
Test cases support advanced settings to optimize browser performance and automate setup. You can define case-level before/after Hooks to prepare pre-conditions or clean up temporary data within the boundary of a single case.
To speed up sequential execution, configure Session Reuse. Reusing browser sessions across serial steps or cases bypasses the slow Workday login and Multi-Factor Authentication (MFA) processes, saving valuable execution time.
Add a case-level "before" hook to perform setup tasks like navigating to a specific workspace.
Add a case-level "after" hook to sign out or clean up records created during the case.
Toggle Session Reuse in the run configuration or case settings to maintain the browser session across sequential runs.
Configure Case Concurrency and Stagger Delays to fine-tune parallel row runs and prevent tenant rate-limiting.
Practical Tips
- Enable Session Reuse specifically for long multi-step processes to drastically cut down execution overhead.
- Ensure case-level hooks clean up any state changes to keep the test environment reproducible.
Test Data Management
Test Cases support tabular data rows that provide dynamic input values to steps during execution. Each column represents a parameter key, and each row represents a distinct set of input values. This allows a single test case to execute multiple times with different data, covering various scenarios without duplicating steps.
You can enter data directly into the table cells, add or remove rows, and leverage templates to reuse common data sets across cases.
Click the "Add" button to insert a new empty row, or choose a saved template from the dropdown to pre-fill a row with template data.
Edit parameter values directly in the table cells by clicking and typing. For detailed editing, click the row number (#) to open the full row editor with form and JSON modes.
Run a single data row by clicking the Play button on the row. Use the Laptop icon to run locally on your machine, or the standard Play icon to run on the server. Click the Stop button (red square) on a running row to cancel it.
Click "Bulk Edit" to open the bulk data editor. Switch between Gherkin-style pipe table format and JSON format. Use the AI prompt feature to generate or transform test data (e.g., "generate 5 rows with realistic employee data").
Save current data as a template via the "Save Template" button (for BP workflows) or use the "Templates" button (for test cases) to create, edit, name, and manage reusable data templates. Apply a template from the "Add" dropdown to populate new rows instantly.
Practical Tips
- Keep test data minimal and focused on the parameters consumed by your steps to avoid unnecessary columns.
- Use the Bulk Editor's AI feature to rapidly generate realistic test data, especially for large datasets.
- Create templates for common data patterns (e.g., "Standard Employee Setup") to save time when adding new test cases.