article thumbnail

The Real Reasons for Doing Test-Driven Development ??

Xebia

Here’s a secret: it’s not for the tests. Learn about the actual goal and values hidden under the surface of Test-Driven Development. Test-Driven Development (TDD) is a controversial topic amongst developers. It is a vehicle to drive development. Why do people apply TDD?

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.

Insiders

Sign Up for our Newsletter

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

article thumbnail

Definition of Done vs. User Stories vs. Acceptance Criteria

Agile Pain Relief Notes from a Tool User

One of the more frequently asked questions in my Scrum workshops is around the difference between Definition of “Done” and Acceptance Criteria , and how they relate to User Stories. While Acceptance Criteria is a commonly understood concept in software development, Definition of “Done” is unique to Scrum. Definition of “Done”.

SCRUM 105
article thumbnail

Stubbing AWS Service calls in Golang

Xebia

But I am also a big fan of test driven development. The testtools.ExitTest(stubber, t) definition will fail the test if a stub that you added was not called. I recently switched to Golang for my language of choice. (In In my previous blog you can read why.) So how do you do this in Golang?

AWS 130
article thumbnail

Bliki: Legacy Seam

Martin Fowler

Once we've found a seam, we can use it to break dependencies to simplify testing, insert probes to gain observability, and redirect program flow to new modules as part of legacy displacement. His definition: “a seam is a place where you can alter behavior in your program without editing in that place”.

article thumbnail

5 ways to do Continuously Improved Testing

Xebia

It is okay to start out simple and not overthink, but these two things are key: Have tests – having some tests is better than no tests, as it provides a feedback mechanism for improvement. This results in a steadily-growing set of tests becoming part of the development cycle.

Testing 130
article thumbnail

Lessons learned from the React Global Online Summit 22 – Junior Track

Apiumhub

Test-Driven Development for Building User Interfaces – Tyler Hawkins. The third presentation, “Test-Driven Development for Building User Interfaces,” was in charge of Tyler Hawkins, Tech Lead at Adobe. getEntriesByName(). getEntriesByType().

UI/UX 87