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
import {YOUR_LAMBDATEST_USERNAME, YOUR_LAMBDATEST_ACCESS_KEY} from "@site/src/component/keys";
43
-
44
-
---
45
-
46
44
**LambdaTest Tunnel** feature allows you to test your **private server URLs** or **locally hosted web-apps** or **websites** on **3000+** real browsers through LambdaTest. However, sometimes corporate firewalls and proxy settings may have restricted you to leverage the LambdaTest Tunnel binary. Not anymore though, as we’ve come up with a new binary for LambdaTest Tunnel. LambdaTest Tunnel follows various protocols such as **Web Socket, HTTPS, SSH(Secure Shell)** etc. to help you establish a secure and unique tunnel connection between your system and LambdaTest cloud servers.
47
45
48
46
You can download the **LambdaTest Tunnel binary** that will help you establish a secure connection through corporate firewalls between your computer and [LambdaTest](https://www.lambdatest.com/) cloud servers for a testing locally hosted website or web-applications. You can test plain **HTML, CSS, PHP, Python** or other similar web files saved on your local system, over combinations of operating systems, browsers, and screen resolutions that are available on LambdaTest.
@@ -55,9 +53,6 @@ You can download the **LambdaTest Tunnel binary** that will help you establish a
## Executing LambdaTest Tunnel for Client Connection
58
-
59
-
---
60
-
61
56
After you download the zip file for your operating system, extract it in a folder and open you command line there. Once you have your terminal routed to the correct directory where the LambdaTest Tunnel binary file is placed, you need to execute the below command.
62
57
63
58
```bash title="Format"
@@ -85,27 +80,15 @@ Once you execute the command, you will successfully establish a client connectio
## What Makes The New LambdaTest Tunnel Binary Special?
88
-
89
-
---
90
-
91
83
Well, other than the fact that you can now establish a connection through your corporate firewalls with the new LambdaTest Tunnel binary. Here are a couple things to top it off -
92
84
93
85
### Auto Update Functionality
94
-
95
-
---
96
-
97
86
Earlier, for every version update in out LambdaTest Tunnel, you were compelled to download the latest binary from our platform and over write it over the outdated version in your computer. Well, now this new binary will take care of that. Every time you execute this binary, it will check for the **latest** version available and will update itself **automatically**, in case it gets outdated.
98
87
99
88
### Default Port 443
100
-
101
-
---
102
-
103
89
Now, by default, everything will run over the **port 443** to ensure a secure web browser communication through **http protocol** over **TLS/SSL**.
104
90
105
91
### Leverage `.lt.yaml` file
106
-
107
-
---
108
-
109
92
With this new LambdaTest Tunnel binary, you can declare your LambdaTest authentication credentials in a **YAML** file configuration and keep it in the same directory as the **LT binary file**. That way, you won’t have to pass the environment variables in the cmd every time you wish to configure the LambdaTest Tunnel. Once you specify these variables in the `.lt.yaml file`, you will just have to execute the binary file through cmd **LT.exe** and the YAML file will automatically configure a secure LambdaTest Tunnel connection by auto detecting the variables specified in the YAML file.
Similarly, you can go ahead and pass any other variables by just specifying them in the YAML file. For example, if you wish to have verbose variable passed on for detailed logs while the binary is being configured. You will add the verbose flag in your YAML file:
124
107
125
-
```
108
+
```yaml
126
109
User: salmank
127
110
Key: 123456789abcdefghijklmnopqrstuv
128
111
TunnelName: LambdaTest
@@ -134,9 +117,6 @@ Now, when you trigger the binary file through cmd. You will have your verbose lo
The **MITM(Man-in-the-middle)** mode enables you to test websites using self-signed certificates on your local system or internal network. It happens very often that you may try to test a website on the localhost which may not have valid SSL certificates before the website is made live. In such cases, you may receive the below error.
By using the tunnel **Info APIs**, you can fetch the current status of the tunnel and can use it to stop the tunnel. You can fetch the current tunnel status using the Info API on the tunnel. Suppose the **InfoAPI** is available on the host over port **8000**, then use the below command to infuse the **InfoAPI** in the tunnel.
The --log-level flag in the LambdaTest CLI is used to specify the desired log level for tunnel logs. This feature enables users to control the verbosity of logs generated during tunnel operations, making it easier to debug or monitor activities as needed.
181
159
182
-
---
160
+
```bash
161
+
--log-level YOUR_LOG_LEVEL
162
+
```
163
+
164
+
#### Supported Log Levels:
165
+
- **info :** Provides informational messages about the general operation of the tunnel.
166
+
- **warn :** Highlights potential issues that might not immediately affect functionality but require attention.
167
+
- **debug :** Outputs detailed logs, including diagnostic information, for troubleshooting purposes.
168
+
- **error :** Displays error messages when something goes wrong in the tunnel operation.
169
+
- **fatal :** Shows critical issues that cause the tunnel to terminate unexpectedly.
183
170
171
+
172
+
## AllowHost In Tunnel
184
173
With the latest tunnel binary release we have introduced the capability to provide the domains which will be resolved from tunnel binary and the rest of the urls will be resolved from our servers. This can speed up the execution of test as the latency will be reduced by transferring data from the tunnel client. You may also use this to restrict the traffic flowing from user’s network.
When this flag is used only requests for provided domains will be routed via tunnel and resolved from the user's network. Requests for domains other than mentioned will be resolved from Lambdatest’s network.
198
187
199
188
## Tunnel Arguments
200
-
201
-
---
202
-
203
189
You can find all the arguments for LambdaTest Tunnel by running the below command in your command line:
Copy file name to clipboardExpand all lines: docs/hyperexecute-job-reports.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -100,4 +100,7 @@ The [Error Categorization Report](/support/docs/error-categorization-report/) re
100
100
- Downloadable data for thorough analysis and resolution.
101
101
102
102
## JUnit XML Report
103
-
The [JUnit XML Report](/support/docs/junit-xml-report/) provides a summary of test results conducted on [Date and Time]. The tests are organized into multiple test suites, with detailed information on execution time, status, and individual test cases.
103
+
The [JUnit XML Report](/support/docs/junit-xml-report/) provides a summary of test results conducted on [Date and Time]. The tests are organized into multiple test suites, with detailed information on execution time, status, and individual test cases.
104
+
105
+
## Karate Report
106
+
[Karate Reports](/support/docs/karate-report/) provide a comprehensive overview of your test execution results, offering detailed insights into test performance, coverage, and failures. With visually appealing and interactive HTML reports, you can quickly analyze test outcomes, debug issues, and share results across teams. These reports are seamlessly integrated into Karate's powerful testing framework, ensuring clarity and efficiency in your test automation journey.
description: Streamline error analysis with the Error Categorization Report. Identify patterns in test failures to enhance quality and efficiency in your testing process.
Karate framework supports generating detailed test execution reports that help visualize test results and insights. On HyperExecute, you can run your Karate tests and configure it to generate and download these reports seamlessly.
38
+
39
+
> Ensure your project is configured with the **Karate framework** and all test scripts are in place.
40
+
41
+
## Steps to Generate Karate 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
+
```yaml
48
+
report: true
49
+
partialReports:
50
+
location: target
51
+
type: html
52
+
frameworkName: karate
53
+
```
54
+
55
+
**Step 3:** Now execute your job by triggering the HyperExecute CLI. You can visit the HyperExecute dashboard to download the report after job completion.
|`video`|true, false| By default, the video is set as true. This capability helps in video recording of the complete screen while the test gets executed. You can record maximum up to 10 minutes. In case you need to turn off the video recording, you can do so by turning off the button on our Desired Capabilities Generator. <br/>If you turn the video flag off, then for Java, it may provide the below piece of code in the capabilities class. <br/>`capabilities.setCapability("video",false);`| TRUE ||Boolean |`capabilities.setCapability(""video"",false);`|Case Sensitive <br />Unable to generate video <br/>Video is not playing in video player |
43
-
|`visual`|true, false| Command by command screenshots will be recorded at each test step. By default the flag is set as off. <br/>**Note:** test execution time will increase if it’s set as ‘true’. <br/>`capabilities.setCapability("visual",true)`;|FALSE |debug |Boolean |`capabilities.setCapability(""visual"",true);`|Case sensitive <br />Unable to generate screenshot <br/>Screenshot is broken |
44
-
|`network`|true, false| Captures a recording for network packets while the test gets executed. By default, the network flag is set as false. <br/>**Note**: test execution time will increase if it’s set as ‘true’. <br/>`capabilities.setCapability("network",true)`; <br /> | FALSE |networkLogs |Boolean |`capabilities.setCapability(""network"",true);`|Case sensitive <br />Network logs not supported|
45
-
|`console`|true, false| JavaScript logs will be recorded for the test. By default, it is set as false. <br/>**Note:** test execution time will increase if it’s set as ‘true’. <br/>`capabilities.setCapability("console",true)```; | FALSE |Capture browser console errors |String |Javascript logs will be recorded for the test. By default, it is set as false. `capabilities.setCapability("console","disable");`|Case Sensitive <br/>No error found <br />Not supported on this browser |
46
-
|`tunnel`|true, false | To test your locally hosted web application with Lambda Tunnel, which establishes an SSH(Secure Shell) connection between your system and our cloud servers. By default, the tunnel flag, will be set as false. <br/>`capabilities.setCapability("tunnel",true);` <br/>Find more about Lambda Tunnel from our documentation to test on [locally hosted web applications.](/docs/testing-locally-hosted-pages/)| FALSE |local |Boolean |`capabilities.setCapability("tunnel",true);`<br/> Find more about LambdaTest Tunnel from our documentation to test on locally hosted web applications. |Case Sensitive <br/>Tunnel not running |
42
+
|`video`|Boolean| By default, the video is set as true. This capability helps in video recording of the complete screen while the test gets executed. You can record maximum up to 10 minutes. In case you need to turn off the video recording, you can do so by turning off the button on our Desired Capabilities Generator. <br/>If you turn the video flag off, then for Java, it may provide the below piece of code in the capabilities class. <br/>`capabilities.setCapability("video",false);`| TRUE ||Boolean |`capabilities.setCapability(""video"",false);`|Case Sensitive <br />Unable to generate video <br/>Video is not playing in video player |
43
+
|`visual`|Boolean| Command by command screenshots will be recorded at each test step. By default the flag is set as off. <br/>**Note:** test execution time will increase if it’s set as ‘true’. <br/>`capabilities.setCapability("visual",true)`;|FALSE |debug |Boolean |`capabilities.setCapability(""visual"",true);`|Case sensitive <br />Unable to generate screenshot <br/>Screenshot is broken |
44
+
|`network`|Boolean| Captures a recording for network packets while the test gets executed. By default, the network flag is set as false. <br/>**Note**: test execution time will increase if it’s set as ‘true’. <br/>`capabilities.setCapability("network",true)`; <br /> | FALSE |networkLogs |Boolean |`capabilities.setCapability(""network"",true);`|Case sensitive <br />Network logs not supported|
45
+
|`console`|Boolean| JavaScript logs will be recorded for the test. By default, it is set as false. <br/>**Note:** test execution time will increase if it’s set as ‘true’. <br/>`capabilities.setCapability("console",true)```; | FALSE |Capture browser console errors |String |Javascript logs will be recorded for the test. By default, it is set as false. `capabilities.setCapability("console","disable");`|Case Sensitive <br/>No error found <br />Not supported on this browser |
46
+
|`tunnel`|Boolean| To test your locally hosted web application with Lambda Tunnel, which establishes an SSH(Secure Shell) connection between your system and our cloud servers. By default, the tunnel flag, will be set as false. <br/>`capabilities.setCapability("tunnel",true);` <br/>Find more about Lambda Tunnel from our documentation to test on [locally hosted web applications.](/docs/testing-locally-hosted-pages/)| FALSE |local |Boolean |`capabilities.setCapability("tunnel",true);`<br/> Find more about LambdaTest Tunnel from our documentation to test on locally hosted web applications. |Case Sensitive <br/>Tunnel not running |
47
47
|`tunnelName`| Your desire tunnel name | To provide the tunnel identifier in your test suite capability when user wants to execute the test through a particular tunnel <br/>`capabilities.setCapability("tunnelName","your desire tunnel name")`;||localName |String |`capabilities.setCapability("tunnelName","your desire tunnel name");`|Case Sensitive <br/>Tunnel not running <br />Tunnel Name not exists |
48
-
|`timezone`| Example: UTC+07:00 | Represents the custom timezone you select for executing a test. <br/>`capabilities.setCapability("timezone","UTC+07:00")`; | UTC+00:00||String |`capabilities.setCapability("timezone","UTC+07:00");`|Case sensitive <br/> Timezone not supported by OS <br />Timezone is different |
48
+
|`timezone`| Example: UTC+07:00 | Represents the custom timezone you select for executing a test. <br/>`capabilities.setCapability("timezone","UTC+07:00")`; | UTC+00:00||String |`capabilities.setCapability("timezone","UTC+07:00");`|Case sensitive <br/> Timezone not supported by OS <br />Timezone is different |
49
+
|`verboseWebDriverLogging`| Boolean | To enable detailed Selenium logs to debug issues of your application using detailed insights including command execution, communication with the browser, and responses. <br />`capabilities.setCapability("verboseWebDriverLogging", true)`| FALSE |
0 commit comments