Beefy Boxes and Bandwidth Generously Provided by pair Networks
laziness, impatience, and hubris

Re^3: Test Driven Development Workflow

by John M. Dlugosz (Monsignor)
on May 20, 2011 at 20:36 UTC ( #905971=note: print w/replies, xml ) Need Help??

in reply to Re^2: Test Driven Development Workflow
in thread Test Driven Development Workflow

It's not that TDD is incompatible with having formal requirements. It's that "Agile" Scum/XP etc. refuse to use the "R" word. The role of having requirements needs to be filled by some other means. For example, the Acceptance Criteria written on the back of the Story Card. TDD and Agile are often used together. Without formal requirements going into a large effort (not a single "story" but a full design that will comprise many stories) something has to take the place of the Requirements. That is often the TDD process.

So if you are using pre-written test cases instead of a document of formal requirements, then it's important to do a good job of it and indeed to write them first.

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://905971]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others exploiting the Monastery: (10)
As of 2016-10-21 15:00 GMT
Find Nodes?
    Voting Booth?
    How many different varieties (color, size, etc) of socks do you have in your sock drawer?

    Results (289 votes). Check out past polls.