Add Category Support to nunitlite Runner

Bug #1172979 reported by Tyrel Alastair Hunter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NUnit Framework
Fix Released
Medium
Charlie Poole
NUnitLite
Fix Released
Medium
Tyrel Alastair Hunter

Bug Description

This Feature is to bring the Category Support from NUnit 3 -> nunitlite so that you can execute all tests in a specified category from using a command line option

Related branches

Changed in nunitlite:
assignee: nobody → Tyrel Alastair Hunter (ialastairhunter)
Revision history for this message
Charlie Poole (charlie.poole) wrote : Re: [Bug 1172979] [NEW] Add Category Support to nunitlite Runner

Thanks for filing this. We need to consider whether to support...

1. include/exclude like the existing nunit-console
2. a more generic filter option, possibly extensible to properties
3. an category expression syntax, as in nunit-console
4. a different syntax

My inclination is to just go for a single option (/include, /filter,
other?) and have a syntax that allows negating choices.

The current syntax with + and - has caused some problems because it doesn't
let categories have a hyphen in their names. I'd be inclined to use and, or
and not in a new syntax.

We could implement it without expressions at first, of course. No need to
do more than what is already needed.

Charlie

On Thu, Apr 25, 2013 at 5:46 PM, Tyrel Alastair Hunter <
<email address hidden>> wrote:

> Public bug reported:
>
> This Feature is to bring the Category Support from NUnit 3 -> nunitlite
> so that you can execute all tests in a specified category from using a
> command line option
>
> ** Affects: nunitlite
> Importance: Undecided
> Assignee: Tyrel Alastair Hunter (ialastairhunter)
> Status: New
>
> ** Changed in: nunitlite
> Assignee: (unassigned) => Tyrel Alastair Hunter (ialastairhunter)
>
> --
> You received this bug notification because you are subscribed to
> NUnitLite.
> https://bugs.launchpad.net/bugs/1172979
>
> Title:
> Add Category Support to nunitlite Runner
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nunitlite/+bug/1172979/+subscriptions
>

Revision history for this message
Tyrel Alastair Hunter (ialastairhunter) wrote :

I have already asked my team to port over the existing functionality as it exists in nunit 3.0 however If we work to define these requirements quickly we could change the way that this feature works for nunitlite. I makes sense to fix some of the issues as we implement the feature if we know that the issues exisit in other versions of nunit

Changed in nunitlite:
status: New → In Progress
Revision history for this message
Charlie Poole (charlie.poole) wrote : Re: [Bug 1172979] Re: Add Category Support to nunitlite Runner

Can you clarify _which_ nunit 3.0 functionality you are loooking at?

There's a test-only runner in the framework project, a public runner in the
console project and a 3.0 version of the nunitlite runner.

Charlie

On Fri, Apr 26, 2013 at 2:30 PM, Tyrel Alastair Hunter <
<email address hidden>> wrote:

> I have already asked my team to port over the existing functionality as
> it exists in nunit 3.0 however If we work to define these requirements
> quickly we could change the way that this feature works for nunitlite. I
> makes sense to fix some of the issues as we implement the feature if we
> know that the issues exisit in other versions of nunit
>
> --
> You received this bug notification because you are subscribed to
> NUnitLite.
> https://bugs.launchpad.net/bugs/1172979
>
> Title:
> Add Category Support to nunitlite Runner
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nunitlite/+bug/1172979/+subscriptions
>

Revision history for this message
Tyrel Alastair Hunter (ialastairhunter) wrote :

This is the response I got from my team when showing them your comment Friday

Thanks for the link. I think I got the /include and /exclude options completely ported over from NUnit to NUnit lite. However, I am still doing some testing to make sure it all works the same, but from what I have tested the /include and /exclude works with single categories as well as multiple categories delimited by commas.


Sent from Mailbox for iPhone

On Sat, Apr 27, 2013 at 1:15 PM, Charlie Poole <email address hidden> wrote:

> Can you clarify _which_ nunit 3.0 functionality you are loooking at?
> There's a test-only runner in the framework project, a public runner in the
> console project and a 3.0 version of the nunitlite runner.
> Charlie
> On Fri, Apr 26, 2013 at 2:30 PM, Tyrel Alastair Hunter <
> <email address hidden>> wrote:
>> I have already asked my team to port over the existing functionality as
>> it exists in nunit 3.0 however If we work to define these requirements
>> quickly we could change the way that this feature works for nunitlite. I
>> makes sense to fix some of the issues as we implement the feature if we
>> know that the issues exisit in other versions of nunit
>>
>> --
>> You received this bug notification because you are subscribed to
>> NUnitLite.
>> https://bugs.launchpad.net/bugs/1172979
>>
>> Title:
>> Add Category Support to nunitlite Runner
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/nunitlite/+bug/1172979/+subscriptions
>>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1172979
> Title:
> Add Category Support to nunitlite Runner
> Status in NUnitLite Testing Framework:
> In Progress
> Bug description:
> This Feature is to bring the Category Support from NUnit 3 ->
> nunitlite so that you can execute all tests in a specified category
> from using a command line option
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/nunitlite/+bug/1172979/+subscriptions

Revision history for this message
Tyrel Alastair Hunter (ialastairhunter) wrote :

Sorry here is the rest of their reply

I will also watch the link on launchpad to see if Charlie Poole has any comments on what should be changed. I did bring over the Category Expressions from NUnit (still haven't completely tested if all operations work), but if we decided not to implement Category Expressions then that should be complete.


Sent from Mailbox for iPhone

On Sat, Apr 27, 2013 at 1:17 PM, Tyrel Alastair Hunter
<email address hidden> wrote:

> This is the response I got from my team when showing them your comment Friday
> Thanks for the link. I think I got the /include and /exclude options completely ported over from NUnit to NUnit lite. However, I am still doing some testing to make sure it all works the same, but from what I have tested the /include and /exclude works with single categories as well as multiple categories delimited by commas.
> —
> Sent from Mailbox for iPhone
> On Sat, Apr 27, 2013 at 1:15 PM, Charlie Poole <email address hidden> wrote:
>> Can you clarify _which_ nunit 3.0 functionality you are loooking at?
>> There's a test-only runner in the framework project, a public runner in the
>> console project and a 3.0 version of the nunitlite runner.
>> Charlie
>> On Fri, Apr 26, 2013 at 2:30 PM, Tyrel Alastair Hunter <
>> <email address hidden>> wrote:
>>> I have already asked my team to port over the existing functionality as
>>> it exists in nunit 3.0 however If we work to define these requirements
>>> quickly we could change the way that this feature works for nunitlite. I
>>> makes sense to fix some of the issues as we implement the feature if we
>>> know that the issues exisit in other versions of nunit
>>>
>>> --
>>> You received this bug notification because you are subscribed to
>>> NUnitLite.
>>> https://bugs.launchpad.net/bugs/1172979
>>>
>>> Title:
>>> Add Category Support to nunitlite Runner
>>>
>>> To manage notifications about this bug go to:
>>> https://bugs.launchpad.net/nunitlite/+bug/1172979/+subscriptions
>>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1172979
>> Title:
>> Add Category Support to nunitlite Runner
>> Status in NUnitLite Testing Framework:
>> In Progress
>> Bug description:
>> This Feature is to bring the Category Support from NUnit 3 ->
>> nunitlite so that you can execute all tests in a specified category
>> from using a command line option
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/nunitlite/+bug/1172979/+subscriptions

Revision history for this message
Charlie Poole (charlie.poole) wrote :
Download full text (3.4 KiB)

As we discussed offline, let's stick with /include and /exclude with single
or comma-separated categories for now in NUnitLite. The category Expression
implementation can be commented out or suppressed by #if. Make sure to do
the same for any support classes.

Since NUnitLite doesn't have any category support right now, this limited
support will be a plus and we can avoid adding a feature that we would
probably remove later on.

On Sat, Apr 27, 2013 at 10:19 AM, Tyrel Alastair Hunter <
<email address hidden>> wrote:

> Sorry here is the rest of their reply
>
>
> I will also watch the link on launchpad to see if Charlie Poole has any
> comments on what should be changed. I did bring over the Category
> Expressions from NUnit (still haven't completely tested if all operations
> work), but if we decided not to implement Category Expressions then that
> should be complete.
>
>
>
>
> —
> Sent from Mailbox for iPhone
>
> On Sat, Apr 27, 2013 at 1:17 PM, Tyrel Alastair Hunter
> <email address hidden> wrote:
>
> > This is the response I got from my team when showing them your comment
> Friday
> > Thanks for the link. I think I got the /include and /exclude options
> completely ported over from NUnit to NUnit lite. However, I am still doing
> some testing to make sure it all works the same, but from what I have
> tested the /include and /exclude works with single categories as well as
> multiple categories delimited by commas.
> > —
> > Sent from Mailbox for iPhone
> > On Sat, Apr 27, 2013 at 1:15 PM, Charlie Poole <email address hidden>
> wrote:
> >> Can you clarify _which_ nunit 3.0 functionality you are loooking at?
> >> There's a test-only runner in the framework project, a public runner in
> the
> >> console project and a 3.0 version of the nunitlite runner.
> >> Charlie
> >> On Fri, Apr 26, 2013 at 2:30 PM, Tyrel Alastair Hunter <
> >> <email address hidden>> wrote:
> >>> I have already asked my team to port over the existing functionality as
> >>> it exists in nunit 3.0 however If we work to define these requirements
> >>> quickly we could change the way that this feature works for nunitlite.
> I
> >>> makes sense to fix some of the issues as we implement the feature if we
> >>> know that the issues exisit in other versions of nunit
> >>>
> >>> --
> >>> You received this bug notification because you are subscribed to
> >>> NUnitLite.
> >>> https://bugs.launchpad.net/bugs/1172979
> >>>
> >>> Title:
> >>> Add Category Support to nunitlite Runner
> >>>
> >>> To manage notifications about this bug go to:
> >>> https://bugs.launchpad.net/nunitlite/+bug/1172979/+subscriptions
> >>>
> >> --
> >> You received this bug notification because you are subscribed to the bug
> >> report.
> >> https://bugs.launchpad.net/bugs/1172979
> >> Title:
> >> Add Category Support to nunitlite Runner
> >> Status in NUnitLite Testing Framework:
> >> In Progress
> >> Bug description:
> >> This Feature is to bring the Category Support from NUnit 3 ->
> >> nunitlite so that you can execute all tests in a specified category
> >> from using a command line option
> >> To manage notifications about this bug go to:
> >> https://bugs.launchpad.net/nunitlite/+b...

Read more...

Changed in nunitlite:
importance: Undecided → Medium
Changed in nunitlite:
milestone: none → 0.9
Changed in nunitlite:
status: In Progress → Fix Committed
Changed in nunitlite:
status: Fix Committed → Fix Released
Changed in nunit-3.0:
status: New → Triaged
importance: Undecided → Medium
milestone: none → 2.9.6
Changed in nunit-3.0:
assignee: nobody → Charlie Poole (charlie.poole)
status: Triaged → Fix Committed
Changed in nunit-3.0:
status: Fix Committed → Fix Released
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.