In depth resources on Kotlin Multiplatform and Testing

Having automated labels makes the Code Review process much safer by preventing merges for broken Pull Requests, ensuring that the main branch is stable

Automated testing is important for efficient software development, catching bugs within minutes and saving valuable developer time. Mutation Testing validates test suites by altering production code logic. When tests pass despite code mutations, it signals missing test cases.

Automating code and architecture checks in the Continuous Integration pipeline can significantly reduce Code Review time and prevent human forgetfulness.

YAML files, which are not that easy to maintain, changes are usually copied and pasted across multiple files. This article shows that there's a better way.

Having automatic verifications is an important part of Software Development, as the project and team grows it becomes crucial that no regressions are introduced into the "main" branch by mistake.

This is a write-up for a talk I gave at Droidcon Berlin 2023, the video version can be found here: Calling Kotlin Multiplatform Coroutines from Swift with the help of KMP-NativeCoroutines - droidconThe official way of using Coroutines from Swift is awkward and has a lot of limitations. These limitations

In Kotlin Multiplatform, writing platform-specific implementations is sometimes necessary. However, these implementations can introduce inconsistencies between platforms if not properly tested and verified. In this article, we will explore how to tackle this problem.

Automated tests are an integral part of developing software, they help catch bugs before they reach the users and save developers time by cutting down manual testing.

Having a good test suite helps with catching regressions / bugs a lot faster, and gives developers more confidence when merging / releasing their product. In this series, I'll share my recommendations for improving your tests.