note
dragonchild
Personally, I would have a way of uniquely identifying each test in your test suite. Then, you can specify in the RT report which test it is. The key is the unique indentifier for each test in the suite. Now, you don't have any difference between "bug tests" and "new dev tests". Frankly, in TDD, you fix bugs the way you write new code - with a test first. A bug report is a requirement. Instead of coming from the business analyst, it comes from the user. Either way, it's still a requirement.
<!-- Node text goes above. Div tags should contain sig only -->
<div class="pmsig"><div class="pmsig-85580">
<p>------
<br><i>We are the carpenters and bricklayers of the Information Age.</i>
<p><i>Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon.</i> - [flyingmoose]
<p>I shouldn't have to say this, but any code, unless otherwise stated, <i>is <b>untested</b></i>
</div></div>
361821
361821