You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 8, 2020. It is now read-only.
actually according to the java beans convention a default constructor must always be supplied, but in order to use the Beast also for "bean-like classes" or say "pojos" it may be nice to have support to test these classes also.
basically there are two kinds of classes without a default constructor:
immutable classes, of which the state can not be changed after creation
the test could mutate the constructor instead of using setters in order to get specific properties or in this case parameters "dirty" and see if it affects the implementations of equals, hashCode and toString
mutable classes, of which the state can be changed after creation
these classes are actually pretty hard to test because one would need to combine the constructor mutation and the setter mutation strategy
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
actually according to the java beans convention a default constructor must always be supplied, but in order to use the Beast also for "bean-like classes" or say "pojos" it may be nice to have support to test these classes also.
basically there are two kinds of classes without a default constructor:
The text was updated successfully, but these errors were encountered: