New answers tagged

0

TDD is just about validating something against predefined checks (usually automation checks). The final outcome or goal of TDD is that all tests (predefined checks) need to pass to define the particular User story as done. Here we define tests parallel/n-1 (means ahead of development) and we won't mark the user story as completed unless all tests pass. ...


1

As others said, it would miss the point. As Kent Beck says in TDD By Example, TDD is about code design. The tests will drive the architecture of your application, by defining its usage step-by-step. The suggested situation, in the end, will transform you into a low-level software architect - probably not efficient because you will become a bottleneck for ...


2

define 'normal' More seriously, writing (failing) tests before writing code is the essence of TDD and BDD. It means designing the tests and then testable code. The result of writing (failing) tests first is that it actually changes how you write the application code, i.e. to be testable. This results in very different code. Small methods are just one ...


1

That's missing the point. TDD is about fast feedback, so a developer write a checks, runs it, it fails, writes the minimal code needed to make the check pass, runs the check again, this time it passes, goes on to write another check, ... I suppose two people can't be this in sync unless you work on one computer and share the keyboard. You can of course treat ...


Top 50 recent answers are included