Re: New assertEquals() for Beans

Some of the people that have been helping maintain JUnit have been
reluctant to add new assertions to JUnit for a few reasons.

- There are a number of really good Java assertion frameworks out there,
like Hamcrest, Fest and Truth
- Once we get an API into JUnit, it is really hard to change it without
breaking people
- As been noted by a few people, we've been a little bit slow getting new
releases of JUnit out, so it might be slow to get bug fixes out.

David created https://github.com/junit-team/junit.contrib for these kinds
of changes, but it hasn't yet taken off.

I'm not necessarily saying that we wouldn't accept a patch like this, but I
would suggest you check to see if one of the other existing assertion
frameworks might be a better fit.

-- Kevin


On Thu, May 15, 2014 at 1:47 AM, [email protected] [junit] <
[email protected]> wrote:

>
>
> Moin!
>
> We already have written a solution based on the java.bean-api which is
> part of the jdk. It just dives recursive into the object-tree and compares
> the properties. If a property is not equal, the property-name will be shown
> in the standard error / fail-message in junit. It already does what we
> want, but it is not open available right now and we would like to use that
> in several projects.
>
> We could create a maven-artefact in our company-maven-repository, to make
> it available for all projects in our company, but we think this might be
> usefull for everyone. Also we think that this is quite a small change and
> it would be far more elegant to include this in junit itself instead of
> creating a new artifact that has only this single feature.
> So we would like to contribute to junit by adding this to the
> Assert-class.
>
> I hope that this is the correct group to get in touch with the
> junit-maintenance. I would be glad to discuss this in depth if you like the
> idea!
>
> Greetings!
> Jan
>  
>