Use annotation processor

Open
#110 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
20/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
build-system

Research direction

No files, tests, or entry points are named. Start by checking how assertion generation currently runs and whether the project already has annotation-processing support. Done would require a defined annotation-driven generation design integrated into test-class compilation, plus agreed validation criteria.

Written by the indexing model from the issue text.

Description

Not an issue but an idea which probably has been looked into before...

An annotation processor which runs while testclasses are being compiled could look at annotations on the testclasses that specify for which runtime classes assertions are needed. That way you don't have to generate anything separately and all the generation knowledge is right next to the test code.

Dominant language
Java
Stars
72
Forks
47
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from assertj/assertj-generator

All issues in assertj/assertj-generator

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.