菜单
Writes Java TestNG classes with @Test groups, @DataProvider, testng.xml suites, parallel thread-count, ITestListener, and SoftAssert. Trigger on TestNG, Surefire suite XML, or dependsOnMethods. Not for pytest/conftest (pytest-skill) or JUnit-only trees.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/Kayforkind/skill-slice --skill testng-skill命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Open a creative mind on the current context and invent a leap the user did not know to ask for — a feature, protocol, CLI, demo, architecture, product move, prose, experiment, or visual. Use when they run /awe-me or /inspire-me, say “awe me” or “inspire me”, want surprise, adjacent possible, make-strange, or are stuck recognizing instead of seeing. Not a brainstorm list. Not /better (quality pass). Not a feasibility grill.
Design, power, run, and analyze statistically valid A/B/N product experiments (sample size, duration, SRM, sequential monitoring, multiple comparisons). Use when pre-registering a test or reading out a controlled split. Not for event instrumentation, funnel diagnosis, wandb ML tracking (weights-and-biases), MVP smoke tests (mvp-scoping-and-risk-test), or RICE scoring (feature-prioritization-frameworks).
Runs Astropy BoxLeastSquares (BLS) on photometric time series: autopower/power grids, depth SNR, odd/even vetting. Use for periodic box-shaped transit dips or eclipsing binaries (Kovács 2002). Not for Transit Least Squares limb-darkened templates, Lomb-Scargle sinusoids, or non-photometric series. API: astropy.timeseries.BoxLeastSquares (Astropy 8).
正在显示 SKILL.md
| name | testng-skill |
| description | Writes Java TestNG classes with @Test groups, @DataProvider, testng.xml suites, parallel thread-count, ITestListener, and SoftAssert. Trigger on TestNG, Surefire suite XML, or dependsOnMethods. Not for pytest/conftest (pytest-skill) or JUnit-only trees. |
| version | 1.0.1 |
| risk | unknown |
| source | https://github.com/LambdaTest/agent-skills/tree/main/testng-skill |
| source_repo | LambdaTest/agent-skills |
| source_type | community |
| date_added | 2026-07-01T00:00:00.000Z |
| license | MIT |
| license_source | https://github.com/LambdaTest/agent-skills/blob/main/LICENSE |
This skill provides production-grade TestNG test generation patterns for Java projects. It covers groups, data providers, parallel execution, XML suite configuration, listeners, soft assertions, and lifecycle annotations. Use the core patterns below for everyday work; load the deep playbook reference when the task requires advanced configuration such as thread-safe drivers, factories, CI/CD integration, or reporting frameworks.
Use this skill when the user needs to generate or configure TestNG tests in Java. Trigger keywords and phrases:
Do not use this skill for JUnit-only projects. If the user mentions JUnit without TestNG, defer to a JUnit skill.
PATH. Verify:
java -version
PATH. Verify:
mvn -version
pom.xml:
<dependency>
<groupId>org.testng</groupId>
<artifactId>testng</artifactId>
<version>7.10.2</version>
<scope>test</scope>
</dependency>
<plugin>
org.apache.maven.plugins
maven-surefire-plugin
3.2.5
testng.xml
testng.xml are LF or CRLF consistently; mixed endings can cause Surefire parsing errors.Determine which TestNG features the user needs:
| Need | Feature |
|---|---|
| Run subsets of tests | Groups (@Test(groups = "smoke")) |
| Feed multiple data sets | @DataProvider |
| Run tests concurrently | Parallel execution in testng.xml |
| Configure multi-env suites | testng.xml suite XML |
| Capture failures, retries, screenshots | @Listeners + ITestListener |
| Collect multiple assertion failures | SoftAssert |
| Cross-browser matrix | @Factory (see playbook §5) |
Use the lifecycle annotation order as a mental model:
@BeforeSuite → @BeforeTest → @BeforeClass → @BeforeMethod → @Test → @AfterMethod → @AfterClass → @AfterTest → @AfterSuite
Basic test with groups:
import org.testng.annotations.*;
import org.testng.Assert;
public class LoginTest {
@BeforeMethod
public void setUp() { /* setup */ }
@Test(groups = "smoke")
public void testLoginSuccess() {
Assert.assertTrue(loginService.login("user@test.com", "password123"));
}
@Test(groups = "regression", dependsOnMethods = "testLoginSuccess")
public void testAccessDashboard() {
Assert.assertNotNull(dashboard.getContent());
}
@Test(expectedExceptions = AuthenticationException.class)
public void testLoginInvalidPassword() {
loginService.login("user@test.com", "wrong");
}
@AfterMethod
public void tearDown() { /* cleanup */ }
}
@DataProvider(name = "loginData")
public Object[][] loginData() {
return new Object[][] {
{"admin@test.com", "admin123", true},
{"user@test.com", "password", true},
{"invalid@test.com", "wrong", false},
};
}
@Test(dataProvider = "loginData")
public void testLogin(String email, String password, boolean expected) {
Assert.assertEquals(loginService.login(email, password), expected);
}
For advanced data providers (Excel, JSON, CSV, parallel, cross-class), load references/playbook.md §4.
testng.xml suite file<!DOCTYPE suite SYSTEM "https://testng.org/testng-1.0.dtd">
<suite name="Regression" parallel="tests" thread-count="5">
<test name="Smoke">
<groups><run><include name="smoke"/></run></groups>
<classes><class name="tests.LoginTest"/></classes>
</test>
<test name="Full">
<groups><run><include name="regression"/><exclude name="flaky"/></run></groups>
<packages><package name="tests.*"/></packages>
</test>
</suite>
Choose the granularity:
<suite parallel="methods" thread-count="5"> <!-- Method level -->
<suite parallel="classes" thread-count="5"> <!-- Class level -->
<suite parallel="tests" thread-count="5"> <!-- Test level -->
For thread-safe driver patterns (ThreadLocal, ConfigReader), load references/playbook.md §3.
SoftAssert soft = new SoftAssert();
soft.assertEquals(user.getName(), "Alice");
soft.assertEquals(user.getAge(), 25);
soft.assertTrue(user.isActive());
soft.assertAll(); // Reports all failures at once
public class TestListener implements ITestListener {
@Override public void onTestFailure(ITestResult result) {
System.out.println("Failed: " + result.getName());
// Take screenshot, log, etc.
}
}
@Listeners(TestListener.class)
public class LoginTest { /* ... */ }
For production listener suites (retry analyzers, screenshot capture, timing), load references/playbook.md §6.
| Task | Command (PowerShell) |
|---|---|
| Run suite | mvn test -DsuiteXmlFile=testng.xml |
| Run group | mvn test -Dgroups=smoke |
| Run single class | mvn test -Dtest=LoginTest |
| Run single method | mvn test -Dtest=LoginTest#testLoginSuccess |
Default TestNG HTML report:
test-output\index.html
Open in a browser:
Start-Process test-output\index.html
For Allure or ExtentReports integration, load references/playbook.md §10.
dependsOnMethods everywhere. Cascading failures make debugging impossible. Prefer independent tests; use dependsOnGroups sparingly for true ordering dependencies.@Test(groups = "...") you cannot run subsets via -Dgroups. Always assign at least one group.@DataProvider for reusable, maintainable data sets.priority ordering as a substitute for independent tests. Priority-based ordering is fragile and breaks when tests are added or removed.parallel="methods" or higher, shared state (e.g., a static WebDriver) will cause race conditions. Use ThreadLocal per-thread drivers.testng.xml on Windows. Ensure consistent LF or CRLF; mixed endings can cause Surefire XML parsing failures.| Bad | Good | Why |
|---|---|---|
dependsOnMethods everywhere | Independent tests | Cascading failures |
| No groups | @Test(groups = "smoke") | Can't run subsets |
| Hard-coded test data | @DataProvider | Reusable |
| Priority ordering | Independent tests | Fragile |
| Shared static driver in parallel | ThreadLocal<WebDriver> | Race conditions |
Assert after every check in long method | SoftAssert.assertAll() at end | Only first failure reported |
For the full 12-problem debugging quick-reference, load references/playbook.md §12.
After generating or modifying TestNG tests, verify with these checkable steps:
Compile the project:
mvn compile test-compile
Expected: BUILD SUCCESS
Run the suite and confirm tests execute:
mvn test -DsuiteXmlFile=testng.xml
Expected: BUILD SUCCESS with Tests run: N, Failures: 0, Errors: 0, Skipped: 0
Run a specific group to confirm group filtering works:
mvn test -Dgroups=smoke
Expected: only tests annotated @Test(groups = "smoke") execute.
Verify the HTML report was generated:
Test-Path test-output\index.html
Expected: True
Verify parallel execution by checking thread count in logs — TestNG logs thread pool usage when parallel is set. Confirm thread-count matches the suite XML value.
Verify data provider invocation count — a test using @DataProvider with 3 data rows should show Tests run: 3 for that single method.
The following reference file contains deep patterns beyond the core skill:
| File | When to Load |
|---|---|
references/playbook.md | When the task requires advanced configuration: Maven/Surefire setup, multi-env suite XML, ThreadLocal drivers, Excel/JSON/CSV data providers, @Factory cross-browser matrix, production listeners (retry, screenshot, timing), Page Object integration, mixed parallel strategies, Allure/ExtentReports, CI/CD (GitHub Actions, Jenkins), or the 12-problem debugging guide. |
| § | Section | Focus |
|---|---|---|
| 1 | Project Setup & Configuration | Maven + Surefire config |
| 2 | Suite XML Configuration | Multi-env, parallel, groups |
| 3 | BaseTest & Thread-Safe Driver | ThreadLocal, ConfigReader |
| 4 | Data Providers (Advanced) | Excel, JSON, CSV, parallel, cross-class |
| 5 | Factory Pattern | Cross-browser matrix |
| 6 | Listeners (Production Suite) | Retry, screenshot, timing |
| 7 | Soft Assertions & Dependencies | Groups, method deps |
| 8 | Page Object Integration | PageFactory, fluent POs |
| 9 | Parallel Execution Strategies | Method/class/test/mixed |
| 10 | Reporting Integration | Allure, ExtentReports |
| 11 | CI/CD Integration | GitHub Actions, Jenkins |
| 12 | Debugging Quick-Reference | 12 common problems |
| 13 | Best Practices Checklist | 14 items |