Open Source Kotlin Software Testing Tools

Kotest is a flexible and comprehensive testing tool for Kotlin with multiplatform support. Powerful, elegant, and flexible test framework for Kotlin with additional assertions, property testing, and data-driven testing. The Kotest test framework enables tests to be laid out in a fluid way and execute them on JVM, Javascript, or native platforms. With built-in coroutine support at every level, the ability to use functions such as test lifecycle callbacks, extensive extension points, advanced conditional evaluation, powerful data-driven testing, and more. The Kotest assertions library is a Kotlin-first multi-platform assertions library with over 300 rich assertions. It comes equipped with collection inspectors, non-deterministic test helpers, soft assertions, modules for arrow, json, kotlinx-datetime and much more.

BetaScout scans the apps installed on your Android device, shows which of them are known to have a Google Play open-testing (beta) program, opens the opt-in page with one tap and reminds you to re-check the ones you are watching, so you catch a free slot when one opens up. The shared beta catalog is updated daily and grows from opt-in community discoveries, verified against Google Play before they are published. You can mark each app's status and keep private notes. If you sign in, BetaScout reads your own testing pages to detect your memberships and whether each program is open or full. It never joins a program on your behalf. There is no telemetry and no analytics; your app list and markings stay on the device. Available in English, Finnish, Spanish, German, French, Italian and Brazilian Portuguese. Source code, issues and discussions: https://github.com/jrs8205/BetaScout

Booster is an easy-to-use, lightweight, powerful and extensible quality optimization toolkit designed specially for mobile applications. The primary goal is to solve quality problems with the increase of APP complexity, such as performance, stability, and package size, etc. Booster provides a collection of modules for performance detection, multithreading optimization, resources index inline, redundant resources reduction, resources compression, system bug fixing, etc. Using booster, the stability of application can be increased by 15% ~ 25%, and the package size can be reduced by 1MB ~ 10MB. Potential performance issues could be found by using Booster, for example, calling APIs that may block the UI thread or main thread, such as I/O APIs. Thread management has always been a problem for developers, especially the threads started by third-party SDKs, starting too many threads may cause OOM, fortunately, these issues can be solved by Booster.

JVM-based program & library for installation testing. Helps determine what changed during an installation/removal or similar process. ChangeScan has been rewritten in Kotlin. Its new home is here: https://github.com/william-hood/ChangeScan

Koarse Grind has been rewritten in Kotlin (hence the 'K'). It's new home is here: https://github.com/william-hood/koarse-grind-kotlin __________________________________ Test Automation framework for Kotlin/Java with an integrated web-based user interface. It is intended for larger-grained testing of an installed & configured product, rather than unit testing.

A library for in-process compilation of Kotlin and Java code, in the spirit of Google Compile Testing. For example, you can use this library to test your annotation processor or compiler plugin.

Tests written with commented GIVEN, WHEN and THEN regions can be transformed by actually wrapping code within basic blocks called issues. This can occur in a nested fashion. Start with Test|TEST, that can wrap any issue. Given|GIVEN can wrap Given|GIVEN, When|WHEN; or Then|THEN issues. When|WHEN can wrap When|WHEN or Then|THEN issues. Then|THEN can only wrap Then|THEN issues. The Kotlin implementation supports 'suspend' functions: for any issue, there are two ("suspendable" and "nonsuspendable") kinds, that can be toggled between, while in the same foremost issue. Each issue can be labelled, and return values from corresponding code blocks can be referred to (or addressed, by nesting level), and searched using labels; wildcard matching is available too. Unlabelled given/then/when are not searchable, their return values are stored as the foremost issue's pending result. Supporting coroutines for unit or instrumented tests in Android is under development.