v5.5.4

Fixes issue 3277.

gradle test --tests "A*" --tests "B*"

All tests from A* and B* were skipped instead of being ran.

This was a regression from 5.4.x, where this used to work. This was because kotest 5.5.3 were using the wrong combinators for combining the inclusion filters.

Contributors:

• @myuwono

5.5.3

Updated JUnit version from 5.7.2 to 5.8.2

Kotest now requires the runtime version of JUnit to be at least 5.8

Note: If your build somehow manages to put both JUnit 5.7 and 5.8 onto the classpath and they load in the wrong order, you might see problems related to ClassOrderer not being found. Please make sure that only JUnit 5.8+ is loaded

v5.5.2

Gradle test filter fixes, by @myuwono #3257
Tag inheritance configuration is now available on AbstractProjectConfig

5.5.1

Fixed an issue where tests where being skipped when filtered out by the full spec name

v5.5.0

Increase max cache prolems flag

5.4.2

Add test for Gradle plugin and fix issues running tests for native ta…

…rgets on Kotlin 1.7+ (#3107)

* Add (currently failing) test for Gradle plugin, and improve warnings generated by plugin when invalid configuration is detected.

* Fix issue where compilation for Kotlin/Native and Kotlin/JS projects would fail if the project uses Kotlin 1.7.

* Fix issue running Kotest tests under Kotlin 1.5.

The current version of Gradle uses Kotlin 1.5, so retaining backwards
compatibility with Kotlin 1.5 allows us to use Kotest to write tests
for Gradle plugins.

Resolves https://github.com/kotest/kotest/issues/3059.

* Fix issue where Gradle plugin tests could fail due to conflicting with other concurrent build tasks.

* Remove Gradle plugin test for now.

See https://github.com/kotest/kotest/pull/3075#issuecomment-1181554021.

* Revert "Remove Gradle plugin test for now."

This reverts commit ec14c550beba282e60a6e10bfad8c07121478a15.

* Disable JS browser test for now.

* Fix issue where no tests are run when targeting a native platform using Kotlin 1.7.

Kotlin 1.7 now uses the embeddable compiler JAR and corresponding
plugins (from "getPluginArtifact" rather than
"getPluginArtifactForNative" in KotestMultiplatformCompilerGradlePlugin)
by default for all platforms.

This means that the "JS" compiler plugin is used by all targets by
default in projects that use Kotlin 1.7+.

As a first step, I've brought the existing native plugin code over to
the "JS" plugin. Next steps are to rename the projects to make their
intention clearer and merge the transformers used by each platform.

* Rename JS compiler plugin project to better reflect its purpose.

* Update package name to match project name.

* Rename "native" compiler plugin project to better reflect its purpose.

* Refactor transformers to share more logic.

* Add tests to ensure Kotest behaves correctly with Kotlin/Native memory model.

* Extract further common functionality.

* Configure project config objects when running on Kotlin/Native.

* Reorder method calls in native transformer to match JS transformer.

* Further consolidate IR generation logic into base Transformer class.

* Fix issues running compiler plugin on modules that do not contain any Kotest tests.

* Add workaround for issues running Gradle plugin tests on GitHub Actions.

* Revert "Add workaround for issues running Gradle plugin tests on GitHub Actions."

This reverts commit 9df35f8df1629f32ed50976719d22a3fe6a85b52.

* Set target JVM versions for all libraries.

* Add Yarn lock file.

* Run Gradle plugin tests in a separate GitHub Actions job.

Co-authored-by: Sam <sam@sksamuel.com>

v5.4.1

Update dependency gradle to v7.5 (#3116)

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>

v5.4.0

Added docs on statistics.

v5.3.0

More memory locally

v5.2.3: update kotlinx-coroutines (#2912)

* update kotlinx-coroutines

* create merge function

* clean up reference

* rm merge function and use copyforChild in mergeForChild

* clean up

* add annotation