菜单
Extracts common setup (base URI, auth, RequestSpecification) from multiple test classes into an abstract base class. Use when the user wants to reduce duplication, add a base test class, or share setup across test classes.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | refactor-tests-base-class |
| description | Extracts common setup (base URI, auth, RequestSpecification) from multiple test classes into an abstract base class. Use when the user wants to reduce duplication, add a base test class, or share setup across test classes. |
Use this skill when the user:
Identify duplication.
Look at the test classes the user pointed at or that live in the same package/module. Note repeated setup: RestAssured.baseURI, given().contentType(...).header("Authorization", ...), .log().ifValidationFails(), etc.
Design the base class.
BaseApiTest) in the same package or a parent package under src/test/java.@BeforeMethod (or @BeforeClass if base URL is static) to build a shared RequestSpecification: base URI, content type, auth header, and .log().ifValidationFails(). Store it in a field (e.g. protected RequestSpecification requestSpec).Refactor test classes.
given(requestSpec).when()... (or given().spec(requestSpec).when()...).@BeforeMethod that only set base URI or auth; keep any setup that is specific to that class (e.g. a resource-specific path constant).Keep tests independent.
Do not put shared mutable state in the base class. Use @BeforeMethod for per-test spec if needed (e.g. fresh spec per test). Follow project rules for test isolation.
Verify.
Run the test suite (mvn test) to ensure all tests still pass. If the user has TestNG groups, run the same groups as before.
getBasePath()) for subclasses that need different paths.Adds authentication (Bearer token, Basic, or API key) to API tests using config or env and a shared RequestSpecification. Use when the user wants to add auth to tests, use a token, or secure requests.
Adds negative API test cases (400, 404, 401, etc.) to an existing test class following project rules. Use when the user wants to add negative tests, cover error cases, or add 404/400 tests.
Adds request and response logging to API tests using Rest Assured's log() (e.g. ifValidationFails) without exposing secrets. Use when the user wants to add logging, debug requests, or log on failure.
Debugs and fixes a failing API test by inspecting assertions, status code, response body, and environment. Use when a test fails, the user pastes a failure message, or they ask why a test is failing.
Runs the AI-powered REST Assured test generator with an OpenAPI/Swagger spec path, then directs the user to the generated test files. Use when the user wants to generate API tests from a spec, points at an OpenAPI file, or says "generate tests for this spec."
Runs the project's API tests with Maven. Use when the user wants to run tests, run the test suite, run smoke tests, or verify tests after changes.