adobe/test

Test Skill — S3Mock

Read docs/TESTING.md, docs/KOTLIN.md, and AGENTS.md (root + relevant module) before writing tests — they define test types, base classes, naming conventions, and running commands.

Key Conventions (from AGENTS.md + docs/TESTING.md)

• Naming: Backtick names: fun `should create bucket successfully`()
• Pattern: Arrange-Act-Assert
• Independence: Each test creates its own resources — no shared state
• Assertions: AssertJ (assertThat(...)) — specific assertions, not just isNotNull()
• Error cases: assertThatThrownBy { ... }.isInstanceOf(AwsServiceException::class.java)
• Visibility: internal class
• Unit under test: name it iut (implementation under test), injected with @Autowired

Base Classes

Always extend the correct base class — never write tests without one:

| Base Class | Test Type | Module | |---|---|---| | ServiceTestBase | Service-layer unit tests | server/ | | StoreTestBase | Store-layer unit tests | server/ | | BaseControllerTest | Controller slice tests (@WebMvcTest) | server/ | | S3TestBase | Integration tests against live Docker container | integration-tests/ |

Integration tests: accept testInfo: TestInfo as a method parameter and use givenBucket(testInfo) for unique bucket names.

Checklist

• [ ] Read docs/TESTING.md and root + module AGENTS.md
• [ ] If existing tests have structural problems (poor naming, shared state, weak assertions), invoke the refactor skill to fix them rather than working around them
• [ ] Verify tests pass locally
• [ ] Cover both success and failure cases
• [ ] Keep tests independent (no shared state, UUID bucket names)
• [ ] Use specific assertions
• [ ] Update copyright year to 2017-<current year> in the header of every file you modify
• [ ] Invoke the lint skill to fix formatting and verify style gates pass