Testing
When you add OpenTelemetry instrumentation to your codebase, you're writing code that needs to be tested like any other code. A function that creates a span, records attributes, and handles errors can have bugs. Without tests, you discover them in production when your traces are missing or incorrect.
Testing
Sampling is one of the most consequential decisions in an observability setup — and one of the least tested. When sampling is misconfigured, you lose exactly the traces you most need: errors, slow requests, and anomalies. Or you over-sample and blow your observability budget. Testing your sampling strategy should be
AWS
AWS EKS adds a Kubernetes control plane on top of AWS infrastructure, which means you're testing both Kubernetes abstractions and AWS-specific behavior. A Pod that works in local kind or minikube may fail in EKS due to IAM Roles for Service Accounts (IRSA), VPC CNI networking, or
Testing
Your OTEL metrics instrumentation is only as good as your confidence that it measures what it claims to measure. A checkout success counter that double-counts, a latency histogram with wrong boundaries, or an alert rule that fires too late (or never) — these are observability bugs that cause real production
AWS
Testing containerized workloads on AWS ECS and Fargate requires a different mindset than testing traditional server-based applications. Your containers are ephemeral, networking is abstracted, and the control plane sits between you and your code. This guide covers practical integration testing patterns for ECS and Fargate workloads. Why ECS/Fargate
Testing
Most teams think of OpenTelemetry as a production concern — you instrument your app, deploy it, and then your observability stack tells you what's happening. CI/CD is where you validate code; OTEL is where you debug production. These two worlds don't meet. This is a missed
Fuzz Testing
Fuzz testing (fuzzing) automatically generates random, malformed, or unexpected inputs and feeds them to your program looking for crashes, hangs, memory corruption, and assertion violations. Modern coverage-guided fuzzers like AFL++ and LibFuzzer generate millions of test cases per second guided by code coverage feedback and have found thousands of
Testing
Orthogonal array testing is one of those techniques that gets mentioned in ISTQB study materials and promptly forgotten because the explanation is usually too abstract to be actionable. It shouldn't be. Orthogonal arrays are a concrete, table-driven approach to combinatorial test design with a clean mathematical basis
Testing
AUTOSAR is the software architecture that underpins most modern ECUs. If you're testing automotive software without understanding AUTOSAR's layering, you're either testing the wrong things or missing entire failure modes. This post covers practical testing strategies for both AUTOSAR Classic (CP) — the real-time
Testing
Decision tables are a test design artifact. Their value is only fully realized when the rules they define become automated tests that run on every build. A decision table sitting in a spreadsheet catches nothing — it's a plan, not a verification. This post covers how to turn a
Testing
OpenXR standardizes XR APIs across runtimes, but runtimes still differ in behavior, extension support, and performance characteristics. Test against each runtime you ship on. Use the Khronos OpenXR Conformance Test Suite for spec compliance, test input paths explicitly against each controller profile, and run your CI against the OpenXR loader
Testing
OpenTofu is the open-source, community-driven fork of Terraform, created after HashiCorp changed Terraform's license from MPL to BSL 1.1 in August 2023. If you've been using Terraform — and especially if you've built tests with Terratest or the native .tftest.hcl framework