You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/deep-dive-into-hyperexecute-yaml.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1095,6 +1095,8 @@ Additional options include:
1095
1095
- **Network**: This is a boolean parameter which when set to true enables network proxy logs for the test.
1096
1096
- **GeoLocation**: This parameter is used to pass the test traffic through a specific geolocation. Value to be passed here is geolocation code
1097
1097
- **FullHar**: This flag generates the HAR logs that offer a comprehensive view of your application's network activity during testing.
1098
+
- **reporterConfigFile**: If your Cypress project does not have a custom reporter configured, `reporterConfigFile` will automatically enable command logs using the mochawesome reporter by default.
1099
+
- **ProjectName**: You can define your project name to autocreate your project in the HyperExecute dashboard.
description: Learn how to configure and generate Robot test execution reports on HyperExecute with step-by-step guidance for seamless test insights and reporting.
Robot Framework is a generic, open-source automation framework designed for acceptance testing, acceptance test-driven development (ATDD), and robotic process automation (RPA). It is widely used in software testing due to its simplicity, extensibility, and ease of use. The framework is keyword-driven, meaning that tests are written using predefined keywords, making it accessible even to non-programmers.
38
+
39
+
> Ensure your project is configured with the Robot framework and all test scripts are in place.
40
+
41
+
## Steps to Generate Robot Reports on HyperExecute
42
+
43
+
**Step 1:** Configure all the necessary dependencies and configurations to your project.
44
+
45
+
**Step 2:** Configure the report parameters in the HyperExecute YAML file
46
+
47
+
Add the following configurations in your YAML file:
**Step 3:** Now execute your job by triggering the HyperExecute CLI. You can visit the HyperExecute dashboard to download the report after job completion.
0 commit comments