fest-assert-2.x
                                
                                 fest-assert-2.x copied to clipboard
                                
                                    fest-assert-2.x copied to clipboard
                            
                            
                            
                        FEST Fluent Assertions 2.x
Each time a an issue is created, github shows a link to CONTRIBUTING.md content.
That's not real bug but it is something that makes me think whether you stop developing my beloved "assert library". What is happening? Why fest-assert job on jenkins is red...
``` java String[] arr = {"a", "b", "c"}; assertThat(arr).containsExactly("a", "b", "c"); // throws AssertionError ``` java.lang.AssertionError: expected: but was:
For code: ``` List z = new ArrayList(Arrays.asList("a","a","a")); assertThat(z).containsExactly("a","a"); ``` Stacktrace: ``` java.lang.ArrayIndexOutOfBoundsException: 2 at org.fest.assertions.internal.Iterables.assertContainsExactly(Iterables.java:995) at org.fest.assertions.api.AbstractIterableAssert.containsExactly(AbstractIterableAssert.java:99) ``` Regards, Wojtek
Your nice library only supports properties of the form getX setX, so this doesn't work ``` java public class Foo { final protected String bar; public Foo(String bar) { this.bar...
Let's see that on an example : ``` java Date date = parseDatetime("2003-04-26T13:01:02"); // 0 ms Date dateMinusOneMs = new Date(date.getTime() - 1); // The assertion below fails as seconds...
I was never comfortable with `isWithinXXX` assertions (event though it was my idea ...), reading them after a while, I find it confusing, if you write ... ``` java assertThat(date).isWithinSecond(otherDate);...
Most (if not all) of the class types for which assertions are provided for have a parent type of `Object`. In practice, the types for which custom assertions will be...
I'd expected the following code to compile successfully: ``` List strings0 = new ArrayList(); List
It would be nice to have be able to write: assertThat(someObject).isEqualOnFields(expectedObject,"id","name"); and assertThat(someObject)..isEqualExcludingFields(expectedObject,"id","name") which would under the hood use a comparator that is doing a reflection equals (similiar to the...