Normal
[Edit]It's consider very bad form to commit failing tests, or test that won't run on everyones computers.[/Edit]Uh, no it's absolutely not. And absolutely fine to have failing tests in a suite until the test is fixed. Committing a test only when it passes is just stupid as it doesnt help other devs know when a failing test gets fixed by fixing another unrelated bug.Furthermore, without these tests you can't see the ratio of how many regressions you have.Just the few cents of someone that has been using xp and tdd for 3 years.
[Edit]
It's consider very bad form to commit failing tests, or test that won't run on everyones computers.
[/Edit]
Uh, no it's absolutely not. And absolutely fine to have failing tests in a suite until the test is fixed. Committing a test only when it passes is just stupid as it doesnt help other devs know when a failing test gets fixed by fixing another unrelated bug.
Furthermore, without these tests you can't see the ratio of how many regressions you have.
Just the few cents of someone that has been using xp and tdd for 3 years.