Beyond TDD: Should I check for failed acceptance tests?

Question

So, you start with an unsuccessful acceptance test and build a function with unit tests until you pass the acceptance test. But how do you go through unit tests, should you check the source control? If you do, do you note that the acceptance test is ignored (and if so, where? In the code or on the build server)? How does this fit into continuous integration?

Answer 1

No, you should not test a failed test; in a continuous integration environment, you must constantly keep the code in an unlocked state; by definition, a failed acceptance test shows that the code is not currently freed.

While its failure, the acceptance test demonstrates that the system does not yet implement this function; when he passes, were made.
_{Growing Object-Oriented Testing Software Steve Freeman and Nat Price}

, , , , , .

, -

43. , . , . , .
_{by Venkat Subramaniam Andy Hunt.}

Answer 2

, , . , , - . , , .

, , , :

• pending , . @wip, .
• , RSpec .

, . , .