Unit test development management best practices
Given:
The development team has people doing the (business-/function-) coding and other people doing UnitTest-coding. For one function it is expected to have more than one unit test. The number of unit test is an effort driver, so effort for unit test coding should be planned and tracked.
Question:
Are there any best practices how to manage this in RTC?
Alternatives:
a) Set up two (execution-level) work items per chunk of work: one for the functional code developer and another one for the unittest-code developer
b) Have only one work item and appropriate states.
c) Have only one work item and use the "Approvals" feature. Make the Unit Test an "approval" for the coding.
Your advice is appreciated.
The development team has people doing the (business-/function-) coding and other people doing UnitTest-coding. For one function it is expected to have more than one unit test. The number of unit test is an effort driver, so effort for unit test coding should be planned and tracked.
Question:
Are there any best practices how to manage this in RTC?
Alternatives:
a) Set up two (execution-level) work items per chunk of work: one for the functional code developer and another one for the unittest-code developer
b) Have only one work item and appropriate states.
c) Have only one work item and use the "Approvals" feature. Make the Unit Test an "approval" for the coding.
Your advice is appreciated.
One answer
I'd suggest (a).
I would only use (b) if the same individual is doing both the
function-coding and the test-coding (which is not the case in your example).
I would only use (c) if the amount of effort needed to write the test
case is so small that it doesn't merit being planned (which is not the
case in your example).
Cheers,
Geoff
tgau wrote:
I would only use (b) if the same individual is doing both the
function-coding and the test-coding (which is not the case in your example).
I would only use (c) if the amount of effort needed to write the test
case is so small that it doesn't merit being planned (which is not the
case in your example).
Cheers,
Geoff
tgau wrote:
Given:
The development team has people doing the (business-/function-) coding
and other people doing UnitTest-coding. For one function it is
expected to have more than one unit test. The number of unit test is
an effort driver, so effort for unit test coding should be planned
and tracked.
Question:
Are there any best practices how to manage this in RTC?
Alternatives:
a) Set up two (execution-level) work items per chunk of work: one for
the functional code developer and another one for the unittest-code
developer
b) Have only one work item and appropriate states.
c) Have only one work item and use the "Approvals" feature.
Make the Unit Test an "approval" for the coding.
Your advice is appreciated.