Skip to content

Commit 9c33dee

Browse files
authored
Merge pull request LambdaTest#1691 from amanchopra1905/stage
testng docs update
2 parents 43bc280 + 8b287f4 commit 9c33dee

File tree

1 file changed

+8
-2
lines changed

1 file changed

+8
-2
lines changed

docs/testng-on-hyperexecute-grid.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -103,7 +103,7 @@ Download the HyperExecute CLI and copy it into the root folder of the downloaded
103103
| Windows | https://downloads.lambdatest.com/hyperexecute/windows/hyperexecute.exe |
104104
| macOS | https://downloads.lambdatest.com/hyperexecute/darwin/hyperexecute |
105105

106-
### Step 2: Setup Hub Endpoints and Capabilites
106+
### Step 2: Setup Hub Endpoints and Capabilities
107107
Update your TestNG test configuration to point to the LambdaTest hub and set capabilities as needed:
108108

109109
```java title="test.java"
@@ -165,7 +165,7 @@ Visit the [HyperExecute Dashboard](https://hyperexecute.lambdatest.com/hyperexec
165165
<img loading="lazy" src={require('../assets/images/hyperexecute/frameworks/selenium/testng/testng_autosplit_1.png').default} alt="automation-dashboard" width="1920" height="868" className="doc_img"/>
166166

167167
## Navigation in Automation Dashboard
168-
Every test run on the HyperExecute has a unique *jobId* associated with it. Each *jobId* can in turn constitute single (or multiple) *groupId*(s). You can visit [HyperExecute Automation Dashboard](https://automation.lambdatest.com/build) for checking the status of the test execution. You can seamlessly navigate between JobId's and taskId's. You need to click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
168+
Click on the *testID* to navigate from the HyperExecute logs to the Automation Dashboard.
169169

170170
<img loading="lazy" src={require('../assets/images/hyperexecute/frameworks/selenium/testng/dashboard2.png').default} alt="automation-dashboard" width="1920" height="868" className="doc_img"/>
171171

@@ -182,6 +182,12 @@ Optimize your test pipeline using the following advanced features:
182182
- 📊 [Detailed Reports](/support/docs/hyperexecute-reports/) – Real-time terminal logs & rich test reports
183183
- 🔄 [Auto-Healing](/support/docs/hyperexecute-auto-healing/) – Automatically recover from certain failures
184184

185+
## Frequently Asked Questions
186+
187+
<details><summary>How to discover Feature Files on HyperExecute</summary> HyperExecute supports intelligent discovery of test scenarios through a built-in utility called <b>[Snooper](/support/docs/hyperexecute-snooper/).</b> It is a discovery tool that identifies and lists Cucumber feature file scenarios to be executed. It works in coordination with the <b>[testRunnerCommand](/support/docs/deep-dive-into-hyperexecute-yaml/#testrunnercommand)</b>, dynamically filtering test cases before execution. </details>
188+
189+
<details><summary>Java Version Setup on HyperExecute</summary> Ensure your tests run with the correct Java version on HyperExecute VMs—matching your local development environment or your project's framework requirements. To install a specific Java version at runtime on a HyperExecute VM, you can use the <b>[runtime](/support/docs/deep-dive-into-hyperexecute-yaml/#runtime)</b> YAML flag.</details>
190+
185191
> For any query or doubt, please feel free to contact us via <span className="doc__lt" onClick={() => window.openLTChatWidget()}>**24×7 chat support**</span> or you can also drop a mail to **[email protected]**.<br />
186192
187193

0 commit comments

Comments
 (0)