Testing
bUnit excels at component-level testing in isolation. But when you need to verify that your Blazor application works correctly in a real browser — handling navigation, authentication, SignalR connections, and JavaScript interop — Playwright is the right tool. This guide covers Playwright end-to-end testing for both Blazor Server and Blazor WebAssembly. Why
Testing
Unit tests verify your ViewModels and services. But you can't verify that buttons are tappable, navigation transitions work correctly, and the app doesn't crash on real gestures without running on a device. .NET MAUI UI testing with Appium (or the older Xamarin.UITest for Xamarin-to-MAUI migrations)
Testing
bUnit is the most capable tool available for Blazor component testing. While the basics of rendering and clicking buttons are well-documented, production Blazor applications involve cascading parameters, render fragments, complex state machines, and JavaScript interop. This tutorial covers all of it. Project Setup for bUnit Create a dedicated test project
Java
Quarkus has become one of the most compelling Java frameworks for building cloud-native microservices. Its supersonic startup time and low memory footprint make it ideal for containers and serverless deployments. But fast startup means nothing if your services aren't properly tested. This guide covers everything you need to
Java
Testing asynchronous code is notoriously tricky. When your application is built on Vert.x — a reactive toolkit where everything happens on an event loop — standard synchronous JUnit assertions don't work. You need to tell JUnit to wait for asynchronous operations to complete before asserting results. The Vert.x
Java
Micronaut's ahead-of-time (AOT) compilation model eliminates reflection-based dependency injection, producing applications that start in milliseconds. This same philosophy extends to testing — Micronaut's test framework (micronaut-test) integrates tightly with JUnit 5 and Spock, giving you fast, deterministic test execution with minimal boilerplate. The Micronaut Testing Philosophy Unlike
Java
Java 21 made virtual threads a permanent feature (JEP 444), fundamentally changing how Java applications handle concurrency. Virtual threads are cheap enough to create one per task — no thread pools required. But testing concurrent code has always been tricky, and virtual threads introduce new patterns and new failure modes that
Java
Helidon is Oracle's open-source Java microservices framework that comes in two flavors: Helidon SE (reactive, functional, no magic) and Helidon MP (MicroProfile-compliant, CDI, JAX-RS). Each flavor has its own testing approach, but both integrate cleanly with JUnit 5 and support Testcontainers for infrastructure dependencies. Understanding the Two Testing
Testing
Deno ships with a built-in test runner. No configuration, no separate test framework, no package.json scripts to set up. Run deno test and you're testing. This guide covers everything in Deno's testing toolkit: Deno.test, the standard assertion library, subtests, test filtering, code coverage, and
Testing
Deno's standard library provides @std/mock for test doubles — spies, stubs, and fake timers. These let you isolate units under test from their dependencies without external mocking libraries. This guide covers everything in @std/mock: spying on function calls, stubbing module methods, mocking fetch, and controlling time in
Testing
Deno KV is a key-value store built into the Deno runtime. In development, it uses SQLite. In Deno Deploy, it uses FoundationDB. Testing KV code correctly means understanding both the API and how to isolate tests from each other. This guide covers testing Deno KV: CRUD operations, atomic transactions, queues,
Testing
Integration tests verify that your Deno application's components work together — that HTTP routes return the right responses, that database queries return the right data, that error handling works end-to-end. They bridge the gap between unit tests (which verify logic in isolation) and E2E tests (which run a real