Add an [Issue] attribute to tests

Bug #1216855 reported by Shay Rojansky
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NUnit Framework
New
Undecided
Unassigned

Bug Description

[Issue now tracked at https://github.com/nunit/nunit-framework/issues/43]

It seems like having an [Issue] attribute, with the URL pointing to a bug tracker page related to the test, would be a useful thing...

Tags: github
Revision history for this message
Charlie Poole (charlie.poole) wrote : Re: [Bug 1216855] [NEW] Add an [Issue] attribute to tests

What behavior would you expect with this? If it's only informational, we
already can support it via PropertyAttribute.
On Aug 26, 2013 3:55 AM, "Shay Rojansky" <email address hidden> wrote:

> Public bug reported:
>
> It seems like having an [Issue] attribute, with the URL pointing to a
> bug tracker page related to the test, would be a useful thing...
>
> ** Affects: nunitv2
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to NUnit
> Extended Testing Platform.
> https://bugs.launchpad.net/bugs/1216855
>
> Title:
> Add an [Issue] attribute to tests
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nunitv2/+bug/1216855/+subscriptions
>

Revision history for this message
Shay Rojansky (roji) wrote :

I thought of It as informational, but its being "standard" would enable GUIs to treat its content as a hyperlink, or to group tests that refer to the same issue, for instance. Nothing beyond a more semantic, standardized approach...

Revision history for this message
Charlie Poole (charlie.poole) wrote :

OK, so this is different and in addition to from your proposed KnownBugAttribute?

affects: nunitv2 → nunit-3.0
Revision history for this message
Shay Rojansky (roji) wrote :

Yes, although both are similar in that they're largely semantic markup of tests, which would be relevant to almost any project (whereas PropertyAttribute is perfect for capturing more project-specific categories, etc).

On another note, I was wondering whether you accept patches and what would be the way to contribute (coming from the github world things seem more complicated :))

Revision history for this message
Charlie Poole (charlie.poole) wrote :

The bug is on GitHub now, along with our source code for nunit 3.0. So now you know what to do. :-)

description: updated
tags: added: github
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.