Swift
Quick and Nimble are the most popular BDD testing libraries for Swift. Quick provides a describe/it DSL for organizing tests; Nimble provides expressive matchers. Together they make test intent clearer than raw XCTest and scale better for complex domain logic. Installation Swift Package Manager // Package.swift or Xcode Package
Kotlin
MockK is the go-to mocking library for Kotlin. Unlike Mockito (which was designed for Java), MockK understands Kotlin's type system — it handles data class, object, companion object, extension functions, coroutines, and final classes without workarounds. Installation // build.gradle.kts testImplementation("io.mockk:mockk:1.13.12"
Kotlin
Kotest is a pure-Kotlin testing framework that goes beyond JUnit 5's Java roots. It offers multiple specification styles, a rich matcher library, built-in property testing, and first-class coroutine support. If you want test code that reads like idiomatic Kotlin, Kotest is worth learning. Installation // build.gradle.kts dependencies
Kotlin
Kotlin runs on the JVM and integrates seamlessly with the Java testing ecosystem. JUnit 5 is the standard choice for Kotlin projects, but Kotlin's language features — named parameters, extension functions, infix notation, and data classes — enable more expressive test code than Java allows. This guide covers how to
Swift
XCUITest is Apple's framework for automating iOS UI interactions. Tests launch the app in a simulator or on a real device, interact with it like a user would, and assert on what appears on screen. Unlike unit tests, UI tests can catch integration issues — broken navigation, missing screens,
Rust
Standard Rust tests don't support parameterized test cases or reusable fixtures out of the box. The rstest crate fills that gap with #[case], #[fixture], #[values], and matrix test generation — all integrating cleanly with cargo test. Installation [dev-dependencies] rstest = "0.23" Copy #[case]: Parameterized Test Cases Without
Rust
Example-based tests check specific cases you've thought of. Property-based tests let the framework generate hundreds of random inputs and find cases you haven't thought of. For Rust, the proptest crate brings property-based testing with automatic failure shrinking into the standard cargo test workflow. What Is Property-Based
Rust
Rust's built-in #[bench] attribute requires nightly and lacks statistical rigor. Criterion.rs is the de facto standard for benchmarking on stable Rust: it handles warm-up, measures statistical variance, compares runs against baselines, and produces HTML reports. Installation [dev-dependencies] criterion = { version = "0.5", features = ["html_reports&
Rust
cargo-nextest is a next-generation test runner for Rust that replaces cargo test with a process-per-test execution model, better terminal output, built-in retry logic, and significantly faster CI runs. It's a drop-in replacement — your existing tests work unchanged. Why nextest? cargo test runs tests in threads within a single
Kotlin
Android has two types of tests: unit tests (JVM, fast) and instrumented tests (run on a device or emulator, access Android APIs). Instrumented tests are required for testing UI behavior, database operations, and anything that depends on the Android framework. This guide covers instrumented tests using Espresso for View-based UI
Rust
Rust ships with a built-in test framework. No extra dependencies, no configuration files — just annotate a function with #[test] and run cargo test. That simplicity is deceptive: the Rust test model covers unit tests, integration tests, doc tests, and benchmarks within a single coherent workflow. This guide covers everything you
Rust
Rust's borrow checker and type system make certain mocking patterns harder than in dynamic languages, but the mockall crate brings first-class mocking support to Rust's test ecosystem. This guide covers the practical patterns you'll reach for in real projects. Why Mock? Mocks replace real