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

Test-Driven Development is not Merely “Test-First”

Net Objectives

Test-first yields analysis, it helps us determine what is clear, what is unclear or missing, and ferrets out misunderstandings. Unit tests are unforgiving, they don’t let you get away with anything. But Test-Driven Development also creates better design.

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: No Bugs

James Shore

That takes time, sure, but it also eliminates time needed for testing and fixing after the fact. It turns out to be a net gain, resulting in higher quality results for less cost and time. According to their coach’s analysis of Capers Jones’ data, an average team would have generated 1,035 defects and delivered 207 to their customer.

article thumbnail

AoAD2 Practice: Fast, Reliable Tests

James Shore

Fast, Reliable Tests. Our tests don’t get in our way. Test-Driven Development. Teams who embrace test-driven development accumulate thousands of tests. The more tests you have, the more important speed and reliability become. Use Broad Tests Only as a Safety Net.

article thumbnail

AoAD2 Practice: Zero Friction

James Shore

Test-Driven Development. Inside the script, use a compiler or linter to tell you when you make syntax errors, and tests to tell you when you make semantic errors. The easiest way is to group your tests into clusters, and run specific clusters based on the files that have changed. Five-Minute Deploy. Nothing else!

article thumbnail

AoAD2 Practice: Reflective Design

James Shore

These relationships are illustrated in figure “Authentication Design Analysis”. Authentication design analysis Next, I needed to identify flaws in the design. Test-Driven Development. I wanted my new login endpoint to have sociable tests. See “Write Sociable Tests” on p.XX.) Test-Driven Development.

article thumbnail

Software Architecture Sonar: most read featured articles

Apiumhub

We work with languages that have big market penetration, with an active community and great support, which also allows us to use the two biggest programming paradigms, object oriented and functional: Java, Kotlin,NET and PHP. We’re talking about Cypress, a tool we might even call a Swiss Army Knife for your tests.