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/ai-test-failure-analysis.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,4 +54,9 @@ To use the AI-powered Test Failure Analysis feature, simply click on the Failure
54
54
55
55
After categorizing errors, we offer a structured approach to address each failure type. You can efficiently get to the precise corrective measures or **Remedies** recommended alng with **Additional suggestions** for the particular error. This targeted approach expedites the issue resolution process, eliminating unnecessary steps and optimizing efficiency.
Copy file name to clipboardExpand all lines: docs/browser-testing-with-real-devices.md
+6-13Lines changed: 6 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,35 +45,28 @@ Below are the steps to run your first browser test on LambdaTest's Real Device C
45
45
46
46
**Step 1:** Login to your LambdaTest account. From the left sidebar, head to Real Device and select **Browser Testing**.
47
47
48
-
<img loading="lazy" src={require('../assets/images/real-device-browser-testing/real-device-browser-home.webp').default} alt="Native Mobile App Testing" className="doc_img" width="1366" height="629"/>
49
-
50
48
**Step 2**: Select the **OS** and **browser** of your choice.
51
49
52
-
<img loading="lazy" src={require('../assets/images/real-device-browser-testing/real-device-browser-browser.webp').default} alt="Native Mobile App Testing" className="doc_img" width="1366" height="629"/>
53
-
54
50
>**Note:** Certain browsers might not be supported on certain devices.
55
51
56
52
**Step 3**: Select the **real device** of your choice. You can also search the preferred real **Android** or **iOS** device in the search bar.
57
53
58
-
<img loading="lazy" src={require('../assets/images/real-device-browser-testing/real-device-browser-testing-os.webp').default} alt="Native Mobile App Testing" className="doc_img" width="1366" height="629"/>
59
-
60
-
61
54
**Step 4**: In the case of **Android** devices, simply enter the website URL in the address bar.
62
-
<img loading="lazy" src={require('../assets/images/real-device-browser-testing/real-browser-testing-android-url.webp').default} alt="Real Device Region Feature" className="doc_img" width="1366" height="629"/>
63
55
64
56
In the case of **iOS** devices, you can enter the website URL once the session has started.
65
57
66
-
67
-
<img loading="lazy" src={require('../assets/images/real-device-browser-testing/real-browser-ios-url.webp').default} alt="Real Device Region Feature" className="doc_img" width="1366" height="629"/>
68
-
69
58
**Step 5**: Select the **Tunnel** option in the top right corner to test your locally hosted and privately hosted websites.
70
59
71
60
Check out our detailed [support documentation](https://www.lambdatest.com/support/docs/testing-locally-hosted-pages/) to learn how to activate the LT Tunnel.
**Step 3:** Download our sample project by clicking on **Download Sample**. (Skip this step if you already have a project you want to test)
94
92
95
93
**Step 4:** Download the [HyperExecute CLI](/support/docs/hyperexecute-cli-run-tests-on-hyperexecute-grid/) as per the OS that you are on.
96
94
97
95
**Step 5:** Select the OS on which you want to run your tests and then download the [HyperExecute YAML](/support/docs/deep-dive-into-hyperexecute-yaml/) file shown on screen. This contains all the configurations required for running tests on HyperExecute.
> **Note**: Your Yaml file should be in the root directory of your project. If you are renaming it, also change the file name in the execution script as well. You can learn more about the advanced configurations [here](/support/docs/deep-dive-into-hyperexecute-yaml/), however for the given sample projects you can simply download the file using the small icon on top right.
104
100
@@ -108,6 +104,13 @@ We will be taking care of everything one by one, just follow the steps given bel
108
104
109
105
**Step 8:** Once your Job is running, you can click on **View Test Results** to navigate to HyperExecute Dashboard where you can see the job getting executed along with the test results.
The generic command required to initiate test execution is given below. You will need to insert the name of your YAML file in place of the `RELATIVE_PATH_OF_YOUR_YAML_FILE` before running this command. (Skip if you already used the command from Step 6. )
Copy file name to clipboardExpand all lines: docs/hyperexecute-task-metrics.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,10 +51,6 @@ The task level view provides insights into the CPU and memory consumption at the
51
51
52
52
By analyzing the task level view, you can pinpoint any tasks that may be causing high CPU or memory usage issues, allowing you to optimize their performance for better overall results.
In the stage level view of HyperExecute, the analysis is segmented into three distinct phases: pre-stage, scenario stage, and post-stage.
@@ -65,6 +61,10 @@ In the stage level view of HyperExecute, the analysis is segmented into three di
65
61
66
62
-**Post-Stage :** The post-stage view concentrates on resource consumption and actions taken after completing the main test scenario. By reviewing the post-stage metrics, you can evaluate resource management efficiency and ensure system stability post-test scenario execution.
0 commit comments