Feature: Generate fluent continuations to Asserts on properties

Open
#220 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
testing, tooling

Research direction

Begin by locating the generator code that creates property assertions and review the existing ListAssert.singleElement() behavior. Confirm how generated and fallback ObjectAssert return types should be selected, then add coverage for the SomeClass/OtherClass example.

Written by the indexing model from the issue text.

Description

We would like to write something like:

@Data
class SomeClass {
    String id;
    OtherClass someField;
}

@Data
class OtherClass {
    String value;
}

@Test
void test() {
    SomeClass someObject = ...;
    assertThat(someObject)
        .hasName("foo")
        .someField()
            .hasValue("abc")
}

That is particularly useful when working on POJO trees as, for example, generated when parsing JSON/YAML documents.
(Inspired by ListAssert.singleElement().)

That is assuming, of course, that we generate the assertions for SomeClass.
The return type would be OtherClassAssert if we generate the assertions for that class as well, of ObjectAssert<OtherClass> otherwise.

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.