HamKrest - Hamcrest for Kotlin
A reimplementation of Hamcrest to take advantage of Kotlin language features.
Note: as of version 188.8.131.52, you must add kotlin-reflect to the classpath to use HamKrest’s reflective features.
Compared to Java:
Kotlin’s type system means that developers don’t have to worry about getting the variance of generic signatures right. Variance is defined on the abstract Matcher type and Kotlin makes sure composition and subtyping work together the way you expect.
Syntactic sugar. You can negate a matcher with the ! operator and compose matchers with infix
import com.natpryce.hamkrest.assertion.assert ... assert.that("xyzzy", startsWith("x") and endsWith("y") and !containsSubstring("a"))
Easier to extend. You can convert named unary predicates into matchers.
val isBlank = Matcher(String::isBlank) assert.that(input, isBlank)
As a shortcut, you can pass named functions to the
orand many other functions that take a matcher.
You can also convert a named binary predicate and the second argument to a matcher for first argument, which works well for extension methods.
fun String.hasLength(n: Int): Boolean = this.length == n val isTheRightLength = Matcher(String::hasLength, 8) assert.that(secretCode, isTheRightLength)
You can use function and property references to match features of a value:
val isLongEnough = has(String::length, greaterThan(8)) assert.that(password, isLongEnough)
All of these shortcuts produce good, human-readable diagnostics.
You can customise how diagnostics are generated by creating a project-specific