- 发行说明
- 入门指南
- 设置和配置
- 自动化项目
- 依赖项
- 工作流类型
- 文件比较
- 自动化最佳实践
- 源代码控件集成
- 调试
- 诊断工具
- 工作流分析器
- 变量
- 参数
- 导入的命名空间
- 录制
- 用户界面元素
- 控制流程
- 选取器
- 对象存储库
- 数据抓取
- 图像与文本自动化
- Citrix 技术自动化
- RDP 自动化
- Salesforce 自动化
- SAP 自动化
- VMware Horizon 自动化
- 日志记录
- ScreenScrapeJavaSupport 工具
- Webdriver 协议
- 测试套件 - Studio
- 扩展程序
- 故障排除

Studio User Guide
- 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\Tests\testFolder01\testCase07.xaml
, the
correspondent mock file is stored as
production\Mocks\Tests\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.
- Nested mocks are unavailable as you cannot use
Surround with Mock
on existing mock activities. - 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. |
|