Add @MaximumSchema support for integration tests
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 28
- Forks
- 25
- Avg merge
- 4d 22h
- Merged PRs (30d)
- 20
Description
Follow-up to PR #1734.
Add a class- and method-level @MaximumSchema execution condition, complementary to @MinimumSchema, so integration tests that verify behavior on older schemas can be skipped once the configured schema exceeds their supported version.
Use it to replace the manual schema assumption in UserListUnsupportedSchemaTestIT.
Acceptance criteria:
@MaximumSchemasupports class and method targets.- Tests above the declared maximum schema are skipped with a clear reason.
UserListUnsupportedSchemaTestITuses the annotation instead ofassumeTrue.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the existing @MinimumSchema execution condition and the UserListUnsupportedSchemaTestIT test, including the manual assumeTrue schema check. Implement the complementary class- and method-level behavior so tests above their maximum are skipped with a clear reason, then replace the manual assumption in UserListUnsupportedSchemaTestIT and run the integration tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100