Test-Driven Development (TDD) FAQs

Question 1

Why are execution gates necessary?

Accepted Answer

Execution gates ensure that code is built, launched, and logs are read before any E2E tests or screenshots are taken. This prevents false positives and ensures the system is actually running as expected.

Question 2

What is the 'Iron Law of TDD' in this skill?

Accepted Answer

The Iron Law mandates that you must write a failing test and see the RED failure output before writing any implementation code. If the test hasn't failed, you haven't practiced TDD.

Question 3

What does this skill consider a 'Fake Test'?

Accepted Answer

A fake test is any check that doesn't verify runtime behavior, such as grepping for a function name, checking internal state instead of user output, or using mocks that defeat the purpose of the test.

Question 4

How does the skill handle documentation?

Accepted Answer

It documents every TDD cycle in a LEARNINGS.md file, recording the specific test command, the observed failure (RED), and the subsequent pass (GREEN) with actual shell output.

Question 5

Does this skill work for GUI and CLI applications?

Accepted Answer

Yes. It includes specific protocols for CLI apps (redirecting stdout to logs) and GUI apps (window-only screenshots and log-file redirection) to ensure evidence-based verification.

Test-Driven Development (TDD)

About

Key Features

Use Cases

Test-Driven Development (TDD)

About

Key Features

Use Cases