Test Failures

[Mark]

After a test has been set up under a story/feature and has been
failed, what is the recommended next step within the product so that
the relevant developer is alerted? Options that come to mind are 1)
create a new defect and link it to the test (can that be done)? 2)
create a new task to fix the problem and link it to the test (can that
be done?) 3) make the developer an owner of the test.

Mark

[Maggie Bullington]

Hi Mark-
You can either create a new Task under the same Story and assign it to the
developer, or create a Defect and assign it to the Developer and link it to
the Story. All linkages are done at the Story/Defect level, not at the
Task/Test level. To link a Story and a Defect, for instance, open the
details page for the Story, find the Relationships grid, and click the
*bold* customize link on the right hand side. Check the "Broken by Defects"
box, and a new section will be added to relationships. You can then assign
Defects to the Story (and vice versa for assigning Stories to a Defect).
Thanks.
-Maggie

[Andy Powell]

My preference is for option 2.

I think creating a defect for a story that has yet to be accepted (and
closed) sends the wrong message. It's okay if the development team has more
work to do on a story based on the results of testing. Creating a defect
allows for the perception that it is new work. It's not new work and it
should be done immediately if the story is at the top of the list.

Option 2 takes a little more time that option 3, but tests don't show up as
work on the Taskboard. I like using tests as only acceptance criteria that
can pass or fail.

Andy

Andy Powell
Andy....@VersionOne.com
(p) 678.268.3343
(f) 770.752.4109
VersionOne | Simplifying Software Delivery
2003-2007 Jolt, TAG, and IT Week Award Winner
Agile Resources @ www.VersionOne.com/Resources/
Agile Blog @ www.agilechronicles.com
Test drive @ www.VersionOne.com

-----Original Message-----
From: versiono...@googlegroups.com
[mailto:versiono...@googlegroups.com] On Behalf Of Mark
Sent: Friday, September 14, 2007 10:48 AM
To: VersionOne-users
Subject: Test Failures

[Mark]

Thanks for the suggestions.

Our approach is now to use the Tests. In the results section, the bugs
are listed 1, 2, 3 with one line descriptions. Then, a separate Note
below is raised for each one detailing specific steps &etc. We've also
added some new status categories to help with the workflow. Our
intention was that the developer would then annotate the Notes after
completing the fix. Unfortunately, as we roll this approach out, it
appears that only the creator of the Note can edit it - is this
intentional or a bug?

Mark

On Sep 14, 6:37 pm, "Andy Powell" <Andy.Pow...@VersionOne.com> wrote:
> My preference is for option 2.
>
> I think creating a defect for a story that has yet to be accepted (and
> closed) sends the wrong message. It's okay if the development team has more
> work to do on a story based on the results of testing. Creating a defect
> allows for the perception that it is new work. It's not new work and it
> should be done immediately if the story is at the top of the list.
>
> Option 2 takes a little more time that option 3, but tests don't show up as
> work on the Taskboard. I like using tests as only acceptance criteria that
> can pass or fail.
>
> Andy
>
> Andy Powell

> Andy.Pow...@VersionOne.com

> (p) 678.268.3343
> (f) 770.752.4109
> VersionOne | Simplifying Software Delivery
> 2003-2007 Jolt, TAG, and IT Week Award Winner
> Agile Resources @www.VersionOne.com/Resources/
> Agile Blog @www.agilechronicles.com
> Test drive @www.VersionOne.com
>
>
>
> -----Original Message-----
> From: versiono...@googlegroups.com
>
> [mailto:versiono...@googlegroups.com] On Behalf Of Mark
> Sent: Friday, September 14, 2007 10:48 AM
> To: VersionOne-users
> Subject: Test Failures
>
> After a test has been set up under a story/feature and has been
> failed, what is the recommended next step within the product so that
> the relevant developer is alerted? Options that come to mind are 1)
> create a new defect and link it to the test (can that be done)? 2)
> create a new task to fix the problem and link it to the test (can that
> be done?) 3) make the developer an owner of the test.
>

> Mark- Hide quoted text -
>
> - Show quoted text -

[Andy Powell]

Mark,

This is behavior by design, although I'm sure you agree that removing or
changing the style of the edit link would make this clearer. I will submit
a defect for that.

Andy Powell
Andy....@VersionOne.com