tdd-workflow

To write integration tests for Flutter WebSocket features using TDD, draft outside-in scenarios first, verify they fail for the right reason, then implement code and run verification through flutter test and scripts/sb-dev.sh.

The best way to structure end-to-end smoke tests is to use an outside-in approach: draft end-to-end scenarios first, keep tests stable during implementation, and validate running app behavior via REST and WebSocket calls through sb-dev.sh.

You should choose unit tests over integration tests based on the change type to avoid unnecessary work while maintaining coverage, selecting the appropriate tier during test-tier planning before writing any failing tests.

Yes, the red-green-refactor TDD workflow requires running unit tests through self-review, followed by integration and end-to-end smoke verification using the project's scripts/sb-dev.sh flow to validate running app behavior.

Yes, you can apply test-driven development to bugfixes and refactors by selecting the right test tiers, writing failing tests first that capture the intended behavior, and verifying end-to-end behavior via sb-dev.sh when applicable.

Integration tests fail before implementation begins in TDD to ensure they fail for the right reason, validating that the test correctly captures the intended behavior before you write the implementation code.