article thumbnail

AoAD2 Practice: Test-Driven Development

James Shore

Test-Driven Development. It’s test-driven development, and it actually delivers these results. Test-driven development, , or TDD, is a rapid cycle of testing, coding, and refactoring. Test-driven development applies the same principle to programmers’ intention.

article thumbnail

AoAD2 Practice: Continuous Integration

James Shore

The integration branch must always build and pass its tests. Without exception, it must always build and pass its tests. Test-Driven Development. Although the term was invented by Jez Humble in 2010, Kent Beck described it as part of continuous integration way back in 2004: Integrate and build a complete product.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

AoAD2 Practice: Feature Toggles

James Shore

Kent Beck calls it a “Keystone” [Beck 2004] (p. Test-Driven Development. This does raise the question: if you can’t see your changes, how do you test them? The answer, of course, is test-driven development and narrow tests. It’s easy: when working on something new, wire up the UI last.

article thumbnail

AoAD2 Practice: Feature Flags

James Shore

Beck 2004] (p. Test-Driven Development. This does raise the question: if you can’t see your changes, how do you test them? The answer, of course, is test-driven development and narrow tests. Strictly speaking, the simplest type of feature flag isn’t a feature flag at all.

article thumbnail

No Fighting In This (Agile) Dojo with M. David Green

Marcus Blankenship - Podcasts

And in an Agile Dojo, typically a team comes together, either because there is a specific development skill that they want to practice, such as, for example, test-driven development, or perhaps they want to practice how they start and stop their programming sessions or how they pair program.

Agile 59
article thumbnail

Agile vs Waterfall: Key Differences And Definition?—?Which Model Is Better?

Codegiant

Test-Driven Development ?—?TDD TDD encourages you to write automated code first and then develop just-enough code in order to pass the test later. It consists of six stages: business modeling, data modeling, process modeling, application generation, testing, and turnover. Domain-Driven Design ?—?Created

Agile 52