fest-assert-2.x
fest-assert-2.x copied to clipboard
alexruiz
FEST Fluent Assertions 2.x
Prefer `%n` format specifier if `String.format` is used or `System.getProperty("line.separator")`.
Returning Iterable is, IMHO, a bad idea. You cannot ask an Iterable about its size, and you cannot access elements by index. The methods that I plan to revert are...
Instead of writing ``` java Iterable actual = Iterable expected = assertThat(actual).containsAll(expected).hasSameSizeAs(expected); ``` i'd like to write ``` java Iterable actual = Iterable expected = assertThat(actual).containsOnly(expected); ``` So i propose...
Exact signature : ``` java public S doesNotContainAnyElementsOf(Iterable
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.
MapEntry should use generics for key and value: MapEntry. Then it makes sense to change the MapAssert.contains(MapEntry) to MapAssert.contains(MapEntry). Maybe even MapEntry
to complete what has been done in #50
Assertions for `Class` objects. It's of limited use but if you are writing a classloader or a code generation library it may be very convenient.
Found org.fest.assertions.internal.Arrays#assertHasSameSizeAs() No formatting applied at all. Goal: - define at least formatting rules - apply them automatically before each commit - don't accept code which does not follow formatting...
