- Release Notes
- Getting Started
- Setup and Configuration
- Automation Projects
- Dependencies
- Types of Workflows
- File Comparison
- Automation Best Practices
- Source Control Integration
- Debugging
- The Diagnostic Tool
- Workflow Analyzer
- About Workflow Analyzer
- ST-NMG-001 - Variables Naming Convention
- ST-NMG-002 - Arguments Naming Convention
- ST-NMG-004 - Display Name Duplication
- ST-NMG-005 - Variable Overrides Variable
- ST-NMG-006 - Variable Overrides Argument
- ST-NMG-008 - Variable Length Exceeded
- ST-NMG-009 - Prefix Datatable Variables
- ST-NMG-011 - Prefix Datatable Arguments
- ST-NMG-012 - Argument Default Values
- ST-NMG-016 - Argument Length Exceeded
- ST-DBP-002 - High Arguments Count
- ST-DBP-003 - Empty Catch Block
- ST-DBP-007 - Multiple Flowchart Layers
- ST-DBP-020 - Undefined Output Properties
- ST-DBP-023 - Empty Workflow
- ST-DBP-024 - Persistence Activity Check
- ST-DBP-025 - Variables Serialization Prerequisite
- ST-DBP-026 - Delay Activity Usage
- ST-DBP-027 - Persistence Best Practice
- ST-DBP-028 - Arguments Serialization Prerequisite
- Variables
- Arguments
- Imported Namespaces
- Recording
- UI Elements
- Control Flow
- Selectors
- Object Repository
- Data Scraping
- Image and Text Automation
- Automating Citrix Technologies
- RDP Automation
- SAP Automation
- VMware Horizon Automation
- Logging
- The ScaleCoordinates Migration Tool
- The ScreenScrapeJavaSupport Tool
- The WebDriver Protocol
- StudioPro
- Extensions
- Troubleshooting
Studio User Guide
Mock Testing
- Create a Process project type.
Note: You can't use the mock feature in Test Automation projects.
- Install the Testing Activities Package
workflowName_mock
and stores
it in Project > Mocks. This folder mirrors the source workflow file
tree structure. For example, if your workflow is stored in the Project tab as
production\Mocks\testFolder01\testCase07_mock.xaml
, the
correspondent mock file is stored as
production\Mocks\testFolder01\testCase07_mock.xaml
.
In a practical scenario, you have an application that writes directly in a database but you want it to write on the screen. You can use Surround with mock to test this specific function, without having to make any changes to your main test case. As a general note, consider using mocks for tests that have permanent effects in production or require special resources.
- Within mock files, you can only edit the mocked activities.
- You can have multiple mock files for a workflow.
- The
mock.json
file contains configuration settings for mock files. - In a Given-When-Then test case structure, Surround with mock is only available for activities within When.
- Changes made in the source workflow file are applied to the mock file when you Save your project. Alternatively, you can manually sync your mock files. For more information, see Mock Testing Actions.
- Synchronization does not work if the mock file is open with changes to be saved.
- Deleting a workflow associated with a mock file prompts you to choose whether you want to remove both files.
- The activity coverage indicator only takes into account the activities included in the source workflow, thus, not calculating any coverage of your mock activities.
The following table lists the actions that you can take for your mock testing.
Action |
Description |
Procedure |
---|---|---|
Create mock workflow |
Create a copy of your main workflow for mock testing. |
|
Remove mock activity |
Remove the mock that surrounds your activity |
|
Surround activity with mock |
Insert a mock activity. |
|
Synchronize mock |
Sync your mock files or folders with the source workflow file or folders, respectively. |
|