The premise of TDD is to write tests that satisfy that a piece of functionality is working as expected.
Be this a unit of code (unit test) or a higher level feature (acceptance test).
A test should be written to fail. (Red)
Simply enough code should be written to make this test pass (Green)
Code should then be tidied up and optimised (Refactor).
This is inline with the Kent Beck model of Red, Green, Refactor for Test Driven Development.
Subscribe to:
Post Comments (Atom)
Lessons from Toyota: How 'True North' Can Transform Your Engineering Team
In the realm of engineering, achieving excellence requires more than just technical proficiency; it demands a clear and unwavering vision. ...
-
"I'm a Celebrity, Get Me Out of Here" has become a cultural phenomenon, captivating audiences worldwide with its thri...
-
The Concept of True North in Lean Methodology In the world of Lean methodology, one of the most fundamental and guiding principles is ...
-
Monorepos are gaining traction in frontend development, with teams looking for better ways to manage shared code, dependencies, and colla...
No comments:
Post a Comment