523-frameworks-micronaut-testing-acceptance-tests

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Implement happy-path acceptance tests from Gherkin for Micronaut using real HTTP and infrastructure.

What is covered in this Skill?

Preconditions: .feature file in context; Micronaut project confirmed
Parsing scenarios tagged @acceptance / @acceptance-tests
BaseAcceptanceTest: @MicronautTest, random port, @Client("/") HttpClient, TestPropertyProvider merging DB + WireMock URLs
wireMock.resetAll() in @BeforeEach when sharing context
Concrete *AT classes: Given/When/Then → setup, HttpClient exchange, AssertJ assertions
Maven three-tier split: *Test → Surefire, *IT + *AT → Failsafe
Happy-path scope by default

Scope: Apply recommendations based on the reference rules and step workflow.

使用真实HTTP和基础设施，为Micronaut实现基于Gherkin的正常流程验收测试。

本Skill涵盖哪些内容？

前置条件：上下文环境中存在.feature文件；已确认是Micronaut项目
解析标记为@acceptance / @acceptance-tests的场景
BaseAcceptanceTest：@MicronautTest、随机端口、@Client("/") HttpClient、合并数据库与WireMock URL的TestPropertyProvider
共享上下文时在@BeforeEach中执行wireMock.resetAll()
具体的*AT类：Given/When/Then → 初始化、HttpClient请求交互、AssertJ断言
Maven三层拆分：*Test → Surefire执行，*IT + *AT → Failsafe执行
默认覆盖正常流程范围

适用范围： 根据参考规则和步骤工作流应用建议。

Do not generate without a .feature file; compile before and verify after.

PRECONDITION: Gherkin
```
.feature
```
file must be in context — stop and ask if not provided
PRECONDITION: The project must use Micronaut — direct the user to @133, @323, or @423 otherwise
MANDATORY: Run
```
./mvnw compile
```
or
```
mvn compile
```
before applying any change
VERIFY: Run
```
./mvnw clean verify
```
or
```
mvn clean verify
```
after applying improvements
BEFORE APPLYING: Read the reference for detailed steps and safeguards

若无.feature文件则不生成代码；执行变更前先编译，变更后再验证。

For detailed guidance, examples, and constraints, see references/523-frameworks-micronaut-testing-acceptance-tests.md.

如需详细指南、示例和约束条件，请查看references/523-frameworks-micronaut-testing-acceptance-tests.md。