Post Closed as "duplicate" by Doc Brown, Bart van Ingen Schenau, gnat, GlenH7, user40980 of
5 deleted 3 characters in body
source | link

Given a large group (50+) of programmers:

I have personally seen what athe wide spectrum tests that are possible for the same problem, even on the first test. So, if TDD is design, how do you know your TDD is optimal for the current problem, and how do you know it is not? Following the first test, is the approach for reviewing the consecutive tests any different, and if so, how?

Given a large group (50+) of programmers:

I have personally seen what a wide spectrum tests that are possible for the same problem, even on the first test. So, if TDD is design, how do you know your TDD is optimal for the current problem, and how do you know it is not? Following the first test, is the approach for reviewing the consecutive tests any different, and if so, how?

Given a large group (50+) of programmers:

I have personally seen the wide spectrum tests that are possible for the same problem, even on the first test. So, if TDD is design, how do you know your TDD is optimal for the current problem, and how do you know it is not? Following the first test, is the approach for reviewing the consecutive tests any different, and if so, how?

4 added 4 characters in body
source | link

Given a large group (50+) of programmers:

I have personally seen what a wide spectrum tests that are possible for the same problem, even on the first test. So, if TDD is design, how do you know your TDD is optimal for the current problem, and how do you know it is not? Following the first test, is the approach for reviewing the consecutive tests any different, and if so, how?

Given a large group (50+) of programmers:

I have personally seen what a wide spectrum tests that are possible for the same problem, even on the first test. So, if TDD is design, how do you know your TDD is optimal for the current problem, and how do you know it is not? Following the first test, is the approach for reviewing consecutive tests any different, and if so, how?

Given a large group (50+) of programmers:

I have personally seen what a wide spectrum tests that are possible for the same problem, even on the first test. So, if TDD is design, how do you know your TDD is optimal for the current problem, and how do you know it is not? Following the first test, is the approach for reviewing the consecutive tests any different, and if so, how?

3 added 95 characters in body
source | link

Given a large group (50+) of programmers:

I have personally seen what a wide spectrum tests that are possible for the same problem, even foron the first test of the same problem. So, if TDD is design, how do you know your TDD is optimal for the current problem, and how do you know it is not? Following the first test, is the approach for reviewing consecutive tests any different, and if so, how?

Given a large group (50+) of programmers:

I have personally seen a wide spectrum tests that are possible, even for the first test of the same problem. So, if TDD is design, how do you know your TDD is optimal for the current problem, and how do you know it is not?

Given a large group (50+) of programmers:

I have personally seen what a wide spectrum tests that are possible for the same problem, even on the first test. So, if TDD is design, how do you know your TDD is optimal for the current problem, and how do you know it is not? Following the first test, is the approach for reviewing consecutive tests any different, and if so, how?

2 deleted 3 characters in body
source | link
1
source | link