JDave vs Kotest comparison of testing frameworks
What are the differences between JDave and Kotest?

JDave

http://jdave.org/

Kotest

https://github.com/kotest/kotest
Programming language

Java

Kotlin

Category

Acceptance Testing

Unit Testing

General info

JDave is a BDD framework for Java

JDave is inspired by RSpec and integrates JMock 2 as mocking framework and Hamcrest as matching library. It uses JUnit adapter to launch JDave specifications. This way it is possible to have IDE, build tool and coverage tool support from day one.

kotest is a powerful, elegant and flexible test framework for Kotlin, formerly known as kotlintest

Kotest has excellent support for data driven testing or table driven testing where it has the ability to quickly rerun the same test over and over with a predefined set of inputs and expected values
xUnit
Set of frameworks originating from SUnit (Smalltalk's testing framework). They share similar structure and functionality.

No

No

Client-side
Allows testing code execution on the client, such as a web browser

Yes

Front-end behaviour can be tested with JDave

Yes

You can test front-end components with kotest
Server-side
Allows testing the bahovior of a server-side code

Yes

JDave can test server-side behaviour

Yes

Yes, you can test back-end components with kotest
Fixtures
Allows defining a fixed, specific states of data (fixtures) that are test-local. This ensures specific environment for a single test

N/A

Yes

kotest contains fixtures, that is the setup / teardown functions
Group fixtures
Allows defining a fixed, specific states of data for a group of tests (group-fixtures). This ensures specific environment for a given group of tests.

N/A

Yes

kotest has group fixtures available
Generators
Supports data generators for tests. Data generators generate input data for test. The test is then run for each input data produced in this way.

N/A

N/A

Licence
Licence type governing the use and redistribution of the software

Apache License 2.0

Apache License 2.0

Mocks
Mocks are objects that simulate the behavior of real objects. Using mocks allows testing some part of the code in isolation (with other parts mocked when needed)

Yes

It integrates JMock 2 as mocking framework

Yes

You can use a third party library like mockk to create mocks
Grouping
Allows organizing tests in groups

Yes

Specifications can be grouped by tagging them with @Group annotation.

Yes

You can create test suites with kotest
Other
Other useful information about the testing framework