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/behave-on-hyperexecute-grid.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -105,7 +105,7 @@ Configure the desired capabilities based on your test requirements. For example:
105
105
]
106
106
```
107
107
108
-
> You can generate capabilities for your test requirements with the help of our inbuilt 🔗 [Capabilities Generator Tool](https://www.lambdatest.com/capabilities-generator/).
108
+
> You can also use **dev** and **beta** browser versions. To generate capabilities for your test requirements, you can use our inbuilt 🔗 [Capabilities Generator Tool](https://www.lambdatest.com/capabilities-generator/).
Copy file name to clipboardExpand all lines: docs/behave-with-selenium-running-behave-automation-scripts-on-lambdatest-selenium-grid.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -198,7 +198,7 @@ def after_all(context):
198
198
}
199
199
]
200
200
```
201
-
> You can generate capabilities for your test requirements with the help of our inbuilt **[Capabilities Generator tool](https://www.lambdatest.com/capabilities-generator/)**.
201
+
> You can also use **dev** and **beta** browser versions. To generate capabilities for your test requirements, you can use our inbuilt 🔗 [Capabilities Generator Tool](https://www.lambdatest.com/capabilities-generator/).
Copy file name to clipboardExpand all lines: docs/capybara-on-hyperexecute-grid.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -107,7 +107,7 @@ Configure the desired capabilities based on your test requirements. For example:
107
107
}
108
108
```
109
109
110
-
> You can generate capabilities for your test requirements with the help of our inbuilt 🔗 [Capabilities Generator Tool](https://www.lambdatest.com/capabilities-generator/).
110
+
> You can also use **dev** and **beta** browser versions. To generate capabilities for your test requirements, you can use our inbuilt 🔗 [Capabilities Generator Tool](https://www.lambdatest.com/capabilities-generator/).
Copy file name to clipboardExpand all lines: docs/codecept-on-hyperexecute.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -98,7 +98,7 @@ By setting up the Hub endpoint, you establish the communication channel between
98
98
99
99
<!-- Configure the desired capabilities based on your test requirements. For example: -->
100
100
101
-
> You can generate capabilities for your test requirements with the help of our inbuilt 🔗 [Capabilities Generator Tool](https://www.lambdatest.com/capabilities-generator/).
101
+
> You can also use **dev** and **beta** browser versions. To generate capabilities for your test requirements, you can use our inbuilt 🔗 [Capabilities Generator Tool](https://www.lambdatest.com/capabilities-generator/).
Copy file name to clipboardExpand all lines: docs/codeception-php-framework.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -159,7 +159,7 @@ modules:
159
159
version: '71.0'
160
160
tunnel: false # sets tunnel value to true for routing traffic through your local machine
161
161
```
162
-
> **Note:**You can generate capabilities for your test requirements with the help of our inbuilt **[Capabilities Generator tool](https://www.lambdatest.com/capabilities-generator/)**.
162
+
> You can also use **dev**and **beta** browser versions. To generate capabilities for your test requirements, you can use our inbuilt 🔗 [Capabilities Generator Tool](https://www.lambdatest.com/capabilities-generator/).
163
163
164
164
### Executing the Test
165
165
**Step 5:** The tests can be executed in the terminal using the following command:
Each [Job](/support/docs/hyperexecute-status/#1-job-level-status) has a [Status](/support/docs/hyperexecute-status/#3-stage-level-status), a unique `Job Number`, a set of [Labels](/support/docs/deep-dive-into-hyperexecute-yaml/#joblabel), info on number of [Tasks](/support/docs/hyperexecute-status/#2-task-level-status) executed as part of that Job, and a `Summary` section followed by the details of the `Job Duration` and who initiated the Job
44
+
All the tests on HyperExecute get executed as a Job. All the Jobs can be found on our [Jobs page](https://hyperexecute.lambdatest.com/hyperexecute). Each [Job](/support/docs/hyperexecute-status/#1-job-level-status) has a [`Status`](/support/docs/hyperexecute-status/#3-stage-level-status), a unique `Job Number`, a set of [`Labels`](/support/docs/deep-dive-into-hyperexecute-yaml/#joblabel), info on number of [`Tasks`](/support/docs/hyperexecute-status/#2-task-level-status) executed as part of that Job, and a `Summary` section followed by the details of the `Job Duration` and who initiated the Job
49
45
50
46
On this page you have other things such as filters, help center, docs, [secrets management](/support/docs/hyperexecute-how-to-save-and-manage-secrets/) and much more. You can also filter through all of the jobs on the basis of the date, status, type etc.
> Learn more about Secrets Management, Getting User Name and Access Key from our [Knowledge Base](/support/docs/hyperexecute-knowledge-base/)
50
+
> Learn more about [Secrets Management](/support/docs/hyperexecute-how-to-save-and-manage-secrets/), getting [User Name and Access Key](/support/docs/hyperexecute-how-to-get-my-username-and-access-key/) from our [Knowledge Base](/support/docs/hyperexecute-knowledge-base/)
55
51
56
52
### Top Panel
57
53
@@ -100,55 +96,33 @@ You can access a much more detailed section for your test cases on the Automatio
100
96
101
97
It provides you with all the necessary data points that you need for your test.
-**Create an Issue**: You can create an issue/tickets on directly onto Slack, Jira etc with the integrations that we provide.
108
-
-**Analytics**: You can access the analytics of all of your tests by clicking on the **Analytics** button.
109
-
-**Access Key**: Your Username and Access Key can be accessed by clicking on the **Access Key** button on the top right-hand side of the dashboard.
110
-
-**Help**: Click on the **Question Mark (?)** icon to access the Help Center.
111
99
### Basic Summary
112
100
You can see the details of your test on the panel on the top of the screen. It contains several details like the browser, the test status, the test name, and more.
-**All Commands**: Each command that is run as a part of your test case is shown here. Each command also contains its own parameters, that can be accessed by hovering on the command and clicking on **View Parameters**.
146
-
147
122
-**Network**: Access the network logs while your tests were getting executed on the **Network** tab.
148
-
149
123
-**Logs**: View all kinds of logs at one place. You can toggle between the **Console Logs**, **Terminal Logs** and the **Test Framework Logs**.
>**Note**: You can download the logs by clicking on the Download button on the top right-hand corner of the logs tab.
154
128
@@ -176,12 +150,6 @@ Additionally, upon redirection, the automation dashboard opens the relevant tab
176
150
177
151
Update your designated HyperExecute YAML file with [`buildConfig`](/support/docs/deep-dive-into-hyperexecute-yaml/#buildconfig) configuration to activate the "**Test Summary Hyperlink**" feature. This configuration allows you to define specific parameters that govern the behavior of the hyperlinks based on the test summary status.
178
152
179
-
## Support
180
-
181
-
If you need more help regarding HyperExecute, click on **Support** to speak to LambdaTest Support. You can also access LambdaTest Support by clicking on the bottom right-hand side of your dashboard.
Dependent tests signify that one test relies on the outcome of another. To achieve this, TestNG offers the '**dependsOnMethods**' attribute within @Test annotations.
40
+
41
+
For instance, consider the code snippet in which '**SignIn()**' depends on '**OpenBrowser()**,' and '**LogOut()**' depends on 'SignIn().'
42
+
43
+
```java
44
+
importorg.testng.annotations.Test;
45
+
publicclassDependsOnTest {
46
+
@Test
47
+
publicvoidOpenBrowser() {
48
+
System.out.println("The browser is opened");
49
+
}
50
+
51
+
@Test (dependsOnMethods = { "OpenBrowser" })
52
+
publicvoidSignIn() {
53
+
System.out.println("User has signed in successfully");
54
+
}
55
+
56
+
@Test (dependsOnMethods = { "SignIn" })
57
+
publicvoidLogOut() {
58
+
System.out.println("The user logged out successfully");
59
+
}
60
+
}
61
+
```
62
+
63
+
To discover and manage dependent tests using the Test Discovery command, you can use the following syntax:
64
+
65
+
```yaml
66
+
mvn test -Dmode=discover -Dplatname=win -Dframework=testng -Ddiscovery=dependent
67
+
```
68
+
69
+
This command will provide a Test Discovery Result that lists the tests and their dependencies, ensuring that dependent tests are executed in the correct order, such as ["Test1#SignIn,Test1#LogOut,Test1#OpenBrowser"].
TestNG provides group-based test discovery functionality. You can specify groups for your tests and execute or exclude specific groups during test runs.
40
+
41
+
To perform group-based test discovery, you can use the ***@BeforeGroups*** and ***@AfterGroups*** annotations in your TestNG tests. These annotations allow you to specify setup and cleanup methods that run before and after specific groups of tests.
42
+
43
+
For example:
44
+
45
+
```java
46
+
publicclassGroupIntegrationTest {
47
+
48
+
@BeforeGroups("database")
49
+
publicvoidsetupDB() {
50
+
System.out.println("setupDB()");
51
+
}
52
+
53
+
@AfterGroups("database")
54
+
publicvoidcleanDB() {
55
+
System.out.println("cleanDB()");
56
+
}
57
+
58
+
@Test(groups="selenium-test")
59
+
publicvoidrunSelenium() {
60
+
System.out.println("runSelenium()");
61
+
}
62
+
63
+
@Test(groups="selenium-test")
64
+
publicvoidrunSelenium1() {
65
+
System.out.println("runSelenium()1");
66
+
}
67
+
68
+
@Test(groups="database")
69
+
publicvoidtestConnectOracle() {
70
+
System.out.println("testConnectOracle()");
71
+
}
72
+
73
+
@Test(groups="database")
74
+
publicvoidtestConnectMsSQL() {
75
+
System.out.println("testConnectMsSQL");
76
+
}
77
+
78
+
}
79
+
```
80
+
81
+
In the Hyperexecute YAML Version 0.2 configuration, you can use the ```discoveryFlags``` parameter to specify the groups to discover during test discovery.
82
+
83
+
```yaml
84
+
framework:
85
+
name: "maven/testng"
86
+
discoveryFlags: ["-Dgroups=database"]
87
+
```
88
+
89
+
Here it will only discover tests belonging to the group database. Use comma-separated values if you want to specify multiple groups.
90
+
91
+
Similarly, you can use the ```excludedGroups``` parameter that can be used to run all test groups except for the defined set of groups.
92
+
93
+
```yaml
94
+
framework:
95
+
name: "maven/testng"
96
+
discoveryFlags: ["-DexcludedGroups=database"]
97
+
```
98
+
99
+
This discovers all test of groups except database.
100
+
101
+
102
+
Alternatively, you can also specify the groups or excluded groups directly in the pom.xml file using the Maven Surefire Plugin
> You can generate capabilities for your test requirements with the help of our inbuilt 🔗 [Capabilities Generator Tool](https://www.lambdatest.com/capabilities-generator/).
166
+
> You can also use **dev** and **beta** browser versions. To generate capabilities for your test requirements, you can use our inbuilt 🔗 [Capabilities Generator Tool](https://www.lambdatest.com/capabilities-generator/).
0 commit comments