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
Currently if a class has a boolean field / property (say hideLegend, the assertion generator produces two methods: isHideLegend() and isNotHideLegend. It would be really helpful to have an additional method hasHideLegend(boolean expectedValue). To keep with the BooleanAssert pattern, this might become hasHideLegendEqualTo(boolean) and hasHideLegendNotEqualTo(boolean). This is demonstrated by the example below:
private void testHelperMethod(MyAssertionClass instanceUnderTest, SomeInput input){
boolean expectedHasLegend = // some code that uses input to determine expected legend;
MyAssertionClassAssert assert = Assertions.assertThat(instanceUnderTest);
if (expectedHadLengeng)
assert.isHideLegend();
else
assert.isNotHideLegend();
}
The above could become:
private void testHelperMethod(MyAssertionClass instanceUnderTest, SomeInput input){
boolean expectedHasLegend = // some code that uses input to determine expected legend;
Assertions.assertThat(instanceUnderTest)
hasHideLegend(expectedHasLegend );
}
The text was updated successfully, but these errors were encountered:
Currently if a class has a boolean field / property (say hideLegend, the assertion generator produces two methods: isHideLegend() and isNotHideLegend. It would be really helpful to have an additional method hasHideLegend(boolean expectedValue). To keep with the BooleanAssert pattern, this might become hasHideLegendEqualTo(boolean) and hasHideLegendNotEqualTo(boolean). This is demonstrated by the example below:
The above could become:
The text was updated successfully, but these errors were encountered: