All Articles
139 articles across 7 topics.
BDD Fundamentals (21)
- Gherkin Examples Tables vs Live Acceptance Criteria
- Gherkin Background Steps & Accumulated State
- Scenario Outline Tables Diverge From Domain
- Gherkin Background Blocks That Outlive Scenarios
- BDD Gherkin vs Given-When-Then Test Cases
- Given, When, Then, And, But: BDD Step Rules
- Scenario Context: Hooks to Step Definitions
- BDD Pipeline Runs for dragon-sod-bdd
- Scenario Outlines Multiply Brittle Step Bindings
- The Three Amigos BDD Workshop That Works
- Page Object vs Screenplay in BDD Frameworks
- Why Gherkin Ubiquitous Language Drifts
- Background Steps Silently Corrupt Isolation
- When Step Definitions Outlive Their Features
- Migrating 500 Selenium Tests to BDD
- Three-Amigos Sessions That Do Not Suck
- What Is BDD (and Why Most Teams Get It Wrong)
- How to Write Gherkin That Actually Scales
- Living Documentation: When BDD Tests Become the Spec
- Outside-In TDD vs BDD: The Real Difference
- The Anatomy of a Good Given/When/Then Step
AI + Testing (24)
- AI Test Generators & Ambiguous Background State
- AI Test Generators Misread Implicit State
- AI Test Generators & Implicit Preconditions
- AI Step Generators & Shared State Misclassification
- Testing Async Architectures Without Guessing
- AI Step Generators & Polymorphic Domain Events
- Java Cucumber Step Regex: A Precise Guide
- AI Test Generators & Overloaded Step Params
- Soft Assertions & Silent BDD Step Failures
- Testing Async Workloads Without Losing Your Mind
- AI Step Generators & Stale Fixture Vocabulary
- Monorepo CI: Run Only Affected Tests
- AI Step Generators & Overloaded Domain Terms
- Audit Event Stream Validation: Query Best Practices
- Context Bleed in AI-Generated BDD Steps
- AI Step Definitions & Ambiguous Domain Language
- AI Step Definitions Drifting From Domain Language
- Why "Replace QA with AI" Misses the Point
- Using ChatGPT to Audit Your Test Coverage
- AI-First Testing Framework: From Context to Execution
- Context-Driven Testing with LLMs: A Build Walkthrough
- Generate Test Cases with AI in Minutes (Real Framework)
- Self-Healing Tests: How They Actually Work
- The Cost of AI-Generated Tests (Real Numbers, 2026)
Automation Frameworks (19)
- Cucumber Dry-Run Masks Missing Steps in CI
- Screenplay Actor State Leaks in Parallel Cucumber
- Step Definition Scope Leaks in Cucumber
- Before Hooks That Swallow Driver Init Failures
- Browser Storage Persists Across Cypress Scenarios
- Browser Context Pooling Breaks Playwright Isolation
- Kafka Validation Automation Tools Compared
- Cucumber World Object State Leaks Across Scenarios
- Cucumber Tag Inheritance Silently Widens Hook Scope
- Step Retry Logic Masks Real Flakiness in Playwright
- Fixture Teardown Order & Silent State Corruption
- Step Definition Registries in Shared Libraries
- Custom Cucumber Expressions and Regex Steps
- Page Object Model vs Screenplay Pattern: Decision Guide
- Playwright vs Selenium for BDD in 2026
- The Six Files Every BDD Project Needs
- Build a Scalable BDD Framework Step-by-Step
- Cucumber-JVM vs Behave vs SpecFlow: Honest Comparison
- Driver Abstraction That Survives a Framework Migration
API & Distributed System Testing (19)
- Provider State Hooks That Break Pact Silently
- Async API Testing: Polling, Retry & Idempotency
- K8s Retry & Eventual Consistency Testing
- Exact String Assertions with Bounded Polling
- Consumer-Driven Contracts Break on Shared Schemas
- Job Status Polling in Eventually-Consistent APIs
- Polling, Retry & UI in Eventually-Consistent Systems
- Idempotent Replay & Hidden State in Contract Fixtures
- Automate Kafka Validations That Actually Stick
- Polling Assertions Mask Async API Failures
- Idempotency Key Mismatches in Contract Tests
- Schema Registry Drift Breaks Contract Tests
- Testing Kafka Event-Driven Flows & Consistency
- Validating Event Streams: Kafka and Beyond
- Testing APIs in Distributed Systems Without Going Insane
- Testing Eventually-Consistent Systems
- Async Testing Patterns That Actually Work
- Contract Testing for Microservices: Pact in Practice
- Distributed Tracing for Test Failures: OpenTelemetry Setup
CI/CD & DevOps Testing (18)
- Shard Affinity Skews Flake Rates After Rebalancing
- Shard Timeouts That Skew Flake Rates
- Shard Rebalancing Skews Flake Rate Baselines
- Shard Timeouts That Silently Drop Hook Execution
- Shard Affinity: Pin Slow Scenarios to One Agent
- Shard Rebalancing & Hook Execution Order
- Retry-Then-Fail CI Hides Flake Root Causes
- CI Splits Scenarios: When Hooks Fire Twice
- Quarantine Queues Let Flaky Tests Sneak Back In
- Retry Budgets Hide Systemic Flake in CI
- Parallel BDD Runs & Shared State Flakiness
- Test Selection in Monorepos: Affected Files Only
- Integrate BDD into CI/CD Pipelines Without Breaking Speed
- Parallelize Test Execution in GitHub Actions
- Shift-Left Testing: What It Actually Means
- Synthetic Tests in Production Pipelines
- Auto-Heal vs Auto-Skip: When to Use Each in CI
- Flake Triage as a CI Citizen
Test Strategy & Architecture (20)
- Ownership Gaps in Step Libraries Skew Risk Maps
- Blast Radius: Step Libraries Across Team Boundaries
- Test Impact Analysis: Playwright Monorepo
- Risk Scores When Deployment Frequency Doubles
- Feature File Ownership Gaps & Suite Blast Radius
- Test Impact Analysis in Monorepos, 2026
- Failure Rate Distributions & Suite Architecture Debt
- Scenario Failure Rates and Suite Debt
- GitHub Actions Test Splitting: Timing Data
- Scenario Risk Scores Expose Coverage Gaps
- Hook Execution Order & Suite-Wide Fixture Reliability
- Step Definition Count as a Maintenance Liability
- Scenario Tags as Unintended Test Policy
- Shared Step Libraries & Suite Blast Radius
- Why the Test Pyramid Is Broken (and What Replaces It)
- Coverage as a Vanity Metric: What to Measure Instead
- Modern Test Strategy for Distributed Systems
- Risk-Based Testing in High-Velocity Teams
- Test Strategy for AI Products
- The Quality Engineering Org Chart in 2026
Build with AI (18)
- AI Test Agents Misroute Retries on Shared Transport
- AI Test Agents: Fixture Calls Across Shards
- Multi-Agent Fixtures & Shared Clock Misalignment
- Multi-Agent Fixtures & Idempotency Key Corruption
- Clock Drift in Multi-Agent Test Fixtures
- Multi-Agent Runners & Shared Fixture Clocks
- AI Test Agents & Fixture State at Tool Handoffs
- Multi-Agent Simulations & Shared Fixture State
- AI Test Agents Lose Context Across Tool Boundaries
- AI Test Agents: Hook Context Misrouting
- Ambient Context Corrupts AI Agent Step Boundaries
- AI Step Hallucinations That Slip Past CI
- From Gherkin to Code: A Real Build Pipeline
- Building a Trading Bot Test Harness
- End-to-End AI Testing System: A Full Walkthrough
- Self-Documenting Tests with LLM-Generated Reports
- Stress-Testing an AI Chatbot with Multi-Agent Simulations
- Build an AI Test Assistant with Memory