article thumbnail

TDD or Test-Last? One Thing at a Time

Xebia

We introduce design to our software. That is precisely what TDD helps with. TDD to Separate Concerns At the core of TDD is its mantra : red, green, refactor. We’re fleshing out the problem piecemeal, specifying behavior we want of the system. Conclusion Do you need TDD to do this?

article thumbnail

TechCrunch+ roundup: Technical due diligence, web3’s promise, how to hire well

TechCrunch

So far, web3 has not paid off on the Promise of the Premise : open source software that runs live on the blockchain. 8 questions to answer before your startup faces technical due diligence. After technical due diligence begins, no amount of storytelling can cover the secrets buried in GitHub and Jira.

Insiders

Sign Up for our Newsletter

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

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). As an aside, TDD is an iterative workflow that involves describing a specific aspect you want to solve in terms of the programming language you’re using. Truly, TDD saved the day!

article thumbnail

The Real Reasons for Doing Test-Driven Development ??

Xebia

Why do people apply TDD? What Are the Real Reasons for Doing TDD? Test-Driven Development (TDD) is a controversial topic amongst developers. After many years of doing TDD daily, I think part of the reason is that some people do not fully grasp the reasons behind TDD. TDD and the Values of XP.

article thumbnail

Agile, Stand-ups, TDD and Code Reviews

The Programmer's Paradox

Clearly, the best way to test any software is with fully automated ‘system’ testing that is thorough enough that it can be used for full regression testing. In its fullest form, it is at least as much code as the thing it is going to test, and you have to build a custom version of it, every time, for every system.

article thumbnail

TDD: primitive obsession ( part 3 )

Apiumhub

Last month we talked about TDD example in software development ( part 1 ) and TDD first cycle ( part 2 ). In this new TDD and primitive obsession article, we will focus on removing duplication and reinforcing the constructors of our entities, something key to have a robust system. TDD: primitive obsession.

article thumbnail

TDD and the OCP

Net Objectives

The Open-Closed Principle (Bertrand Myers, Ivar Jacobsen) states, “Software entities (such as classes, modules, and functions) should be open for extension, but closed for modification.”