Specify a webhook-driven task for OpenClaw
Describe event inputs, validation, deduplication, and intended actions before integration work.
5,433,077 AI resources indexedWorking toward the world’s largest AI resource index.
Write and review backend tests with JUnit5, MockMvc, and Spring Boot Test. Use for writing controller tests, service tests, and integration tests.
---
name: backend-testing-a7679a03a9ee
description: Write and review backend tests with JUnit5, MockMvc, and Spring Boot Test. Use for writing controller tests, service tests, and integration tests.
---
# Backend Testing Skill
## When to Use
- Writing unit tests for services or repositories
- Writing controller tests with MockMvc
- Writing integration tests
- Reviewing test coverage or test quality
---
## Stack
- JUnit5 + Spring Boot Test
- MockMvc for controller tests
- (Optional) Testcontainers for integration tests
---
## Mandatory Rules
- **Mocking Annotation:** Do NOT use `@MockBean`. You MUST use **`@MockitoBean`** when replacing a bean in the Spring Test Context.
- **Spying Annotation:** Do NOT use `@SpyBean`. Use **`@MockitoSpyBean`** instead.
- **Best Practices:** Do not recommend or include `@MockBean` in any test examples, guides, or code reviews within this project.
---
## Minimum Requirements
Each endpoint requires:
- At least 1 success test
- At least 1 failure test
Document important endpoints with Spring REST Docs.
---
## What to Test
1. **Validation errors** - Invalid input handling
2. **Authorization errors** - If applicable
3. **Idempotency behaviors** - Duplicate request handling
4. **TTL expiry behaviors** - Session/token expiration
---
## Test Organization
```
src/test/java/
├── controller/
│ └── {Feature}ControllerTest.java
├── service/
│ └── {Feature}ServiceTest.java
└── integration/
└── {Feature}IntegrationTest.java
```
---
## Test Naming Convention
```java
@Test
void should_ReturnSuccess_When_ValidInput() { }
@Test
void should_ThrowException_When_InvalidInput() { }
```
---
name: backend-testing-a7679a03a9ee
description: Write and review backend tests with JUnit5, MockMvc, and Spring Boot Test. Use for writing controller tests, service tests, and integration tests.
---
# Backend Testing Skill
## When to Use
- Writing unit tests for services or repositories
- Writing controller tests with MockMvc
- Writing integration tests
- Reviewing test coverage or test quality
---
## Stack
- JUnit5 + Spring Boot Test
- MockMvc for controller tests
- (Optional) Testcontainers for integration tests
---
## Mandatory Rules
- **Mocking Annotation:** Do NOT use `@MockBean`. You MUST use **`@MockitoBean`** when replacing a bean in the Spring Test Context.
- **Spying Annotation:** Do NOT use `@SpyBean`. Use **`@MockitoSpyBean`** instead.
- **Best Practices:** Do not recommend or include `@MockBean` in any test examples, guides, or code reviews within this project.
---
## Minimum Requirements
Each endpoint requires:
- At least 1 success test
- At least 1 failure test
Document important endpoints with Spring REST Docs.
---
## What to Test
1. **Validation errors** - Invalid input handling
2. **Authorization errors** - If applicable
3. **Idempotency behaviors** - Duplicate request handling
4. **TTL expiry behaviors** - Session/token expiration
---
## Test Organization
```
src/test/java/
├── controller/
│ └── {Feature}ControllerTest.java
├── service/
│ └── {Feature}ServiceTest.java
└── integration/
└── {Feature}IntegrationTest.java
```
---
## Test Naming Convention
```java
@Test
void should_ReturnSuccess_When_ValidInput() { }
@Test
void should_ThrowException_When_InvalidInput() { }
```
Imported from the listed AgentSkill.sh category. Complete supplied package files and notices are retained. Required external tools and credentials are not installed. No bundled code was executed during import. Individual agent task behavior has not been tested.