Our great sponsors
| strikt | hamkrest | |
|---|---|---|
| 2 | 2 | |
| 528 | 341 | |
| - | - | |
| 6.6 | 0.0 | |
| 5 months ago | over 3 years ago | |
| Kotlin | Kotlin | |
| Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
strikt
Posts with mentions or reviews of strikt.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-06.
-
Kotlin assertion libraries - JUnit, Hamkrest and Strikt
In this episode we first look at improving our use of JUnit, using kotlin.test to improve type safety, and assertAll to make multiple checks on the same subject. Then we look at Hamkrest (https://github.com/npryce/hamkrest), a Kotlin reimplementation of the classic Hamcrest, before settingly on Strikt (https://strikt.io/) for our fluent assertions.
-
Which assertion library do you use?
Has anyone compared Strikt with AssertK? I'm especially interested in the number of matchers.
hamkrest
Posts with mentions or reviews of hamkrest.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-01-06.
-
Kotlin assertion libraries - JUnit, Hamkrest and Strikt
In this episode we first look at improving our use of JUnit, using kotlin.test to improve type safety, and assertAll to make multiple checks on the same subject. Then we look at Hamkrest (https://github.com/npryce/hamkrest), a Kotlin reimplementation of the classic Hamcrest, before settingly on Strikt (https://strikt.io/) for our fluent assertions.
-
Which assertion library do you use?
Then you should give Hamkrest a try
What are some alternatives?
When comparing strikt and hamkrest you can also consider the following projects:
Kotest - Powerful, elegant and flexible test framework for Kotlin with additional assertions, property testing and data driven testing
atrium - A multiplatform expectation library for Kotlin
Kluent - Fluent Assertion-Library for Kotlin
aspen - Aspen is a simple test runner for Kotlin that allows you to write tests using your own DSL.
mockito-kotlin - Using Mockito with Kotlin
Elmyr - A utility to make Kotlin/Java tests random yet reproducible
mockk - mocking library for Kotlin
expekt - BDD assertion library for Kotlin