Joel Costigliola

Make Fest Assertions more type safe

1

Each class/interface that has S (self type) parameter should specify an upper bound. it makes the code more type safe as the returned assertion object is considered by the compiler...

Prefer `%n` format specifier if `String.format` is used or `System.getProperty("line.separator")`.

Exact signature : ``` java public S doesNotContainAnyElementsOf(Iterable

FileAssert "String like" assertions on file content

4

New File assertions (inspired by StringAssert) : ``` java assertThat(actualFile).startsWith(""); assertThat(actualFile).contains("Hello"); assertThat(actualFile).matches("*Hello*"); ``` Error messages should mention the charset used to perform comparison.

to complete what has been done in #50

ListAssert : add isEqualTo(T... elements)

1

Handy to method to avoid user to have to create a List when using `isEqualTo(List other)`. By the way, does the same as `containsExactly(T ...)`. I'm not sure we can...

Doc to add from fest assert 1.x confluence doc : - JUnit-Specific Features (http://docs.codehaus.org/display/FEST/JUnit-Specific+Features) - Custom error message (http://docs.codehaus.org/display/FEST/Custom+Error+Messages) - Comparing to Hamcrest (http://docs.codehaus.org/display/FEST/Comparing+to+Hamcrest)

For the time being, we can only post stuff but not modify the pages.