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)
Stacked Pull Requests Are Now Mainstream. Your Review Model Needs to Catch Up
On 6 October, GitHub made stacked pull requests generally available. The feature allows engineers to break one substantial change into a s...
-
The Concept of True North in Lean Methodology In the world of Lean methodology, one of the most fundamental and guiding principles is ...
-
As engineering teams grow, so does the need for leadership that isn’t purely managerial. Enter the Staff Engineer —a senior individual contr...
-
Serverless architectures have redefined backend development, offering scalability and cost-efficiency without the overhead of managing serve...
No comments:
Post a Comment