tdd

To write TDD tests for NG component pattern methods, you should invoke target methods directly, reset interfering state before each run for isolation, and cover all if/else branches to ensure exact code paths are exercised predictably.

The best way to isolate NG component tests is to reset interfering state before each test run, ensuring predictability by preventing previous test executions from affecting the current method invocation and its verified outcomes.

To verify API names and ensure branch coverage when testing NG components, utilize your project's existing tooling to check API names and explicitly test all if/else branches within pattern methods like OnDirtyLayoutWrapperSwap.

No, you do not need extra testing tools to apply these TDD guidelines; the approach requires nothing beyond your project's existing unit-testing framework and conventions to validate method naming and test isolation.

You should avoid magic numbers in NG component unit tests to maintain clarity and robustness; the guidelines mandate a self-checklist and the avoidance of hard-coded magic numbers to ensure deterministic and maintainable test structures.