article thumbnail

The Real Reasons for Doing Test-Driven Development ??

Xebia

Why do people apply TDD? 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. What Are the Real Reasons for Doing TDD? Test-Driven Development (TDD) is a controversial topic amongst developers.

article thumbnail

TDD saved the day

Xebia

To tackle each operation, I started with a small test, following the principles of Test-Driven Development (TDD). If the tests became too complex, I knew something was missing. This was convenient as it allowed me to maintain a TDD flow without external dependencies. Truly, TDD saved the day!

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: Test-Driven Development

James Shore

To share your thoughts, join the AoAD2 open review mailing list. 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. Why TDD Works.

article thumbnail

A Next Step Beyond Test Driven Development

Honeycomb

The most successful software development movement of my lifetime is probably test-driven development or TDD. With TDD, requirements are turned into very specific test cases, then the code is improved so the tests pass. That step is observability driven development.

article thumbnail

5 ways to do Continuously Improved Testing

Xebia

It reduces the cost of testing and supports keeping long-term, high-development velocities. Test automation is not a project or a one-off—it is part of the development lifecycle and should be seen as its own system that needs to evolve over time as the requirements and system under test change and mature.

Testing 130
article thumbnail

5 Tips for Successfully Implementing Behavior-Driven Development in Your Team

Gorilla Logic

It enhances your existing Agile approach , synthesizing Test-Driven Development (TDD) and Acceptance Test-Driven Development (ATDD). You start by defining the desired behavior of the software in terms of concrete examples or scenarios that describe the behavior of the system in a clear, concise way.

article thumbnail

Quality Management is Risk Management

Xebia

This is basically assuming the system is correct until proven otherwise. Deciding what strategy to use depends on your risk appetite for a specific system or functionality and on how much certainty you already have. When the risk profile of a system , or the certainty on it changes, the best quality strategy might also change.