Tagged articles
mutation testing
14 articles · Page 1 of 1
This article exposes how unit test coverage metrics mislead management by counting executed code without verifying correctness, demonstrates with examples how tests lacking assertions create false confidence, explains Goodhart's Law in testing, warns that AI-generated tests amplify the problem by boosting coverage without ensuring quality, and advocates mutation testing and TDD to ensure tests actually catch bugs.
AI codingGoodhart's LawTDD
0 likes · 10 min read

This article presents a comprehensive evaluation framework for AI SRE agents that audits tool usage, execution trajectories, evidence provenance, safety constraints, and environmental outcomes — not just final answer correctness — using deterministic contract tests, real-model trials, mutation testing, and statistical release gates to ensure reliable, auditable automation.
AI SRE AgentCI/CDGo
0 likes · 62 min read

The article explains why simply adding a reviewer AI agent after a developer agent fails when both share requirement misunderstandings, and proposes a structured multi-agent review process: independent judgment against acceptance criteria first, automated mechanical checks, risk-based review division, actionable findings with trigger conditions and verification steps, reverse test validation via mutation and negative testing, and review conclusions tied to specific commits with expiration tracking.
AI code reviewGoogle engineering practicescode review best practices
0 likes · 10 min read

Meta's JiTTesting generates temporary, diff-specific test probes that run on both parent and new code versions to catch behavioral differences introduced by AI-generated changes, using dual pipelines (Dodgy Diff and Intent-Aware), noise reduction via RubFake and LLM-as-Judge, and human-in-the-loop review, while promoting stable passing tests to the permanent hardening suite.
AI-generated codeCI/CDJiTTesting
0 likes · 11 min read

JiTTesting introduces a dual-track testing strategy—permanent hardening tests for regression prevention and temporary catching tests generated on-demand to detect behavioral differences in AI-generated code diffs—using parallel pipelines, automated noise reduction, and human-in-the-loop validation to keep pace with rapid AI-driven development.
AI-assisted testingJiTTestingLLM-based testing
0 likes · 10 min read

The article outlines seven counter-intuitive principles for maintaining code quality when using AI coding agents, arguing that faster AI generation demands stronger engineering discipline, automated quality gates over long prompts, context isolation via short-lived agents, human-defined architecture boundaries, iterative development over detailed planning, junior developers mastering fundamentals before directing agents, and adapting principle thresholds to AI workflows.
AI agentsCRAP analysisContext Management
0 likes · 10 min read

This 20k-word article shares production lessons from building AI coding agents: prompts hit diminishing returns so constraints must move into frameworks; orchestration requires runtime sovereignty; evaluation needs executable criteria like mutation kill rates; humans shift from code review to judgment gates; and nested verification loops replace trust with verifiable facts.
AI coding agentsAgent OrchestrationHuman-AI Collaboration
0 likes · 77 min read

Uncle Bob proposes a 5-agent Gauntlet pipeline (Specifier, Coder, Cleaner, Hardener, QA) with context isolation, externalized rules, recalibrated thresholds, and human oversight of architecture boundaries, enabling small-step iterations where agents prove correctness via mutation testing and CRAP metrics while humans govern module dependencies and review evidence packages.
AI-assisted codingCRAP metricGauntlet pipeline
0 likes · 8 min read


FunTesterAug 17, 2026 · Artificial Intelligence
An exploratory evaluation shows that forcing AI coding agents to follow strict Test‑Driven Development does not improve design or mutation‑testing scores and can inflate token usage several‑fold, suggesting that result‑based feedback is a more effective control mechanism.
AI codingAgentic Codingmutation testing
0 likes · 15 min read

This article shares practical experience migrating Spring Boot integration tests to Testcontainers, covering database migration with Flyway, test data factories, multi-container networking, performance optimization via container reuse and parallel execution, CI pipeline integration, and team conventions for test layering and mutation testing.
CI/CDDatabase TestingDocker
0 likes · 19 min read

This article explains mutation testing, its role in assessing test case quality, introduces the Java tool PITest, outlines a step‑by‑step workflow, presents mutation coverage results, and describes common mutation operators such as condition boundary, negated conditionals, and increments.
PITestmutation testingquality assurance
0 likes · 5 min read

This article explains the fundamentals of fuzz testing, describes its core concepts and step‑by‑step process, compares mutation‑based and generation‑based test case generation algorithms, and details the popular open‑source AFL tool, its workflow, mutation strategies, and practical advantages.
AFLTest Case Generationfuzz testing
0 likes · 8 min read

The article details how China Construction Bank's software development center enhanced code quality and accelerated delivery by integrating unit testing, test‑driven development, mutation testing, automated test code generation, code‑style scanning, and shared template mechanisms within a mature DevOps pipeline.
Code ScanningDevOpsautomation
0 likes · 8 min read

This article explains why evaluating test case effectiveness matters, defines effectiveness as the ratio of discovered bugs to total bugs, and introduces mutation testing with a fully automated robot that injects bugs, runs tests, compares results, and reports a quantitative effectiveness score.
mutation testingquality assurancesoftware testing
0 likes · 8 min read
