<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Testing and quality | SpecDD</title><link>https://specdd.ai/how-to/testing-and-quality/</link><description>Spec-driven development testing and quality guides for deriving tests from specs, finding coverage gaps, running quality gates, using CI, and preventing regressions.</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://specdd.ai/how-to/testing-and-quality/index.xml" rel="self" type="application/rss+xml"/><item><title>How to use SpecDD with TDD</title><link>https://specdd.ai/how-to/testing-and-quality/how-to-use-specdd-with-tdd/</link><guid>https://specdd.ai/how-to/testing-and-quality/how-to-use-specdd-with-tdd/</guid><description>Use spec-driven development with TDD by reviewing the governing spec, deriving a failing test from it, implementing inside spec authority, and keeping specs and tests aligned.</description></item><item><title>How to use SpecDD with BDD</title><link>https://specdd.ai/how-to/testing-and-quality/how-to-use-specdd-with-bdd/</link><guid>https://specdd.ai/how-to/testing-and-quality/how-to-use-specdd-with-bdd/</guid><description>Use spec-driven development with BDD by turning reviewed Scenario blocks into behavior tests while preserving ownership, non-goals, and implementation boundaries.</description></item><item><title>How to define acceptance criteria for implementation</title><link>https://specdd.ai/how-to/testing-and-quality/how-to-define-acceptance-criteria-for-implementation/</link><guid>https://specdd.ai/how-to/testing-and-quality/how-to-define-acceptance-criteria-for-implementation/</guid><description>Define implementation acceptance criteria with spec-driven development by turning behavior, boundaries, scenarios, and Done when entries into testable review targets.</description></item><item><title>How to find test coverage gaps from specs</title><link>https://specdd.ai/how-to/testing-and-quality/how-to-find-test-coverage-gaps-from-specs/</link><guid>https://specdd.ai/how-to/testing-and-quality/how-to-find-test-coverage-gaps-from-specs/</guid><description>Find test coverage gaps from SpecDD specs in a spec-driven development workflow by tracing Must, Scenario, Handles, Raises, Returns, Must not, and Done when entries to actual checks.</description></item><item><title>How to run quality gates after SpecDD changes</title><link>https://specdd.ai/how-to/testing-and-quality/how-to-run-quality-gates-after-specdd-changes/</link><guid>https://specdd.ai/how-to/testing-and-quality/how-to-run-quality-gates-after-specdd-changes/</guid><description>Run quality gates after spec-driven development changes by checking spec syntax, implementation behavior, tests, linting, type checks, docs, and review evidence.</description></item><item><title>How to use specs in CI</title><link>https://specdd.ai/how-to/testing-and-quality/how-to-use-specs-in-ci/</link><guid>https://specdd.ai/how-to/testing-and-quality/how-to-use-specs-in-ci/</guid><description>Use SpecDD specs in CI for spec-driven development by linting changed specs, running relevant project checks, protecting boundaries, and reporting spec-driven verification evidence.</description></item><item><title>How to prevent regressions with local specs</title><link>https://specdd.ai/how-to/testing-and-quality/how-to-prevent-regressions-with-local-specs/</link><guid>https://specdd.ai/how-to/testing-and-quality/how-to-prevent-regressions-with-local-specs/</guid><description>Prevent regressions with local SpecDD specs in a spec-driven development workflow by capturing bug behavior, adding regression scenarios, deriving focused tests, and preserving boundaries.</description></item><item><title>How to review whether a spec is testable</title><link>https://specdd.ai/how-to/testing-and-quality/how-to-review-whether-a-spec-is-testable/</link><guid>https://specdd.ai/how-to/testing-and-quality/how-to-review-whether-a-spec-is-testable/</guid><description>Review whether a SpecDD spec is testable in a spec-driven development workflow by checking observable behavior, deterministic outcomes, concrete scenarios, measurable Done when, and reviewable constraints.</description></item><item><title>How to choose the right test level from a spec</title><link>https://specdd.ai/how-to/testing-and-quality/how-to-choose-the-right-test-level-from-a-spec/</link><guid>https://specdd.ai/how-to/testing-and-quality/how-to-choose-the-right-test-level-from-a-spec/</guid><description>Choose the right test level from a SpecDD spec in a spec-driven development workflow by matching unit, integration, end-to-end, contract, snapshot, static, or benchmark checks to the governed behavior.</description></item><item><title>How to test negative constraints</title><link>https://specdd.ai/how-to/testing-and-quality/how-to-test-negative-constraints/</link><guid>https://specdd.ai/how-to/testing-and-quality/how-to-test-negative-constraints/</guid><description>Test spec-driven development negative constraints by choosing practical checks for Must not behavior, Forbids dependency boundaries, forbidden calls, and regression guards.</description></item><item><title>How to test authorization rules from specs</title><link>https://specdd.ai/how-to/testing-and-quality/how-to-test-authorization-rules-from-specs/</link><guid>https://specdd.ai/how-to/testing-and-quality/how-to-test-authorization-rules-from-specs/</guid><description>Test authorization rules from SpecDD specs in a spec-driven development workflow by deriving checks for roles, permissions, allowed and denied actions, bypass attempts, and boundary cases.</description></item></channel></rss>