Testing
Drone CI Testing: Lightweight Docker-Based Test Pipelines
Drone CI is a container-native CI/CD platform that uses Docker for every step of the pipeline.
Testing
Latest
Testing
BuildKite Testing: Parallel Test Runs and Test Analytics
Buildkite takes a different approach to CI/CD. Rather than running builds on Buildkite's infrastructure, you run Buildkite Agents on your own machines or cloud. Buildkite coordinates the work; your infrastructure executes it. This gives you full control over the build environment while keeping the pipeline management in
Testing
Running Tests in TeamCity: Complete Setup Guide
TeamCity is JetBrains' CI/CD server, widely used in Java and .NET shops but capable of building anything.
Testing
Azure DevOps Pipelines for Testing: YAML, Test Plans, Reporting
Azure DevOps is Microsoft's end-to-end DevOps platform, combining repositories (Azure Repos), CI/CD (Azure Pipelines), project tracking (Azure Boards), test management (Azure Test Plans), and artifact hosting (Azure Artifacts) in one product. For .NET teams and Microsoft-stack organizations, Azure DevOps Pipelines offers deep integration with
Testing
Testing in Bitbucket Pipelines: Jest, Pytest, Playwright
Bitbucket Pipelines is Atlassian's built-in CI/CD service. If your team uses Bitbucket repositories, Pipelines is already available — no separate CI server to provision or maintain. Its tight integration with Jira, Bamboo, and the rest of the Atlassian ecosystem makes it a natural choice for Atlassian-first
Rust
Testing WASM Modules with Wasmtime: Unit Tests, WASI, and Sandboxing
Wasmtime is a fast, standards-compliant WebAssembly runtime from the Bytecode Alliance. Its Rust crate lets you load, instantiate, and call WASM modules from a Rust host — making it ideal for host-side unit tests that verify WASM module behavior, test WASI system calls in a controlled sandbox, and validate
WebAssembly
Benchmarking and Profiling WebAssembly: Criterion, Wasmer, and Flamegraphs
WebAssembly performance is close to native — but "close" needs to be measured. Whether you're evaluating the overhead of crossing the WASM/JS boundary, comparing execution speed between runtimes, or profiling where your WASM module spends its time, you need specific tools: Criterion for Rust-level benchmarks,
Testing
Prism: Spin Up a Mock Server from Your OpenAPI Spec
API-first development means writing your OpenAPI specification before writing code.
Testing
Mock Service Worker (MSW): Intercept API Calls in Tests
Most API mocking libraries intercept calls at the code level — patching fetch, wrapping axios, or monkey-patching network modules.
Rust
Testing Rust WebAssembly with wasm-pack: wasm-bindgen-test in Browser and Node.js
wasm-pack is the standard toolchain for building and testing Rust code compiled to WebAssembly. Its wasm-pack test command runs your Rust tests inside a real browser (headless Chrome, Firefox, or Safari) or under Node.js, giving you confidence that your WASM module behaves correctly in the environments where
Testing
Mountebank: Multi-Protocol Service Virtualization for Testing
Most API mocking tools only speak HTTP. That's fine for REST APIs, but modern systems include gRPC services, legacy TCP protocols, SMTP servers, and binary protocols that HTTP-only tools can't touch. Mountebank is a service virtualization tool that handles multiple protocols through a unified interface.
Go
Testing Go Compiled to WebAssembly: syscall/js, wasip1, and wasm_exec
Go has had WebAssembly support since Go 1.11 via GOARCH=wasm GOOS=js, and since Go 1.21 via the WASI target GOOS=wasip1. Testing Go WASM code requires a different test runner than the standard go test command — either the wasm_exec.js Node.js harness for browser-