Re: Failed Acceptance Test workflow

[Lee Cunningham]

Hi Elize,
Typically, what we see teams doing is this: when an Acceptance Test
underneath a Story fails, the Acceptance Test is put into "Fail"
status, the team members talk to each other, and a Task is created
under the Story for the dev rework. This is in keeping with the
iterative work within the team, and keeps you from having to clog the
system with Defects that have to be associated with Stories. One the
rework is done and Acceptance Test runs successfully, its status is
set to "Pass". Additionally, the Acceptance Test's history will have
a record of those status changes.

Hope this helps.

On Jul 4, 11:59 am, Elize <evanheer...@edge-ka.com> wrote:
> Hi,
>
> I am unclear as to the workflow when an acceptance test fails?  Do I
> generate a new defect associated with the story or do I assign the failed
> story back to the developer in totality?  My next question is - how do I
> rerun the test without losing test history, once the particular story is
> ready for testing again.  I'm currently duplicating the test and re-running
> it, but that seem a bit wrong?
>
> Thanks
> Elize