nunit-core team mailing list archive

[Charlie Poole <charlie@xxxxxxxxx>]

This bug was marked invalid for reasons indicated in the comments and
bug #881617 was spawned to cover making invalid categories more obvious.
That bug was fixed with the release of 2.6.0.

Part of the fix is that invalid categories don't show up in the GUI.
This is intentional, since they can't be selected. More to the point,
the test shows up as red in the GUI and a message is issued in the
console runner.

If you have further ideas for improvement, please file a new issue or
add a comment to #881617 for NUnit 3.0.

-- 
You received this bug notification because you are a member of NUnit
Developers, which is subscribed to NUnit V2.
https://bugs.launchpad.net/bugs/881357

Title:
  CategoryAttribute accepts categories with invalid characters

Status in NUnit Test Framework:
  Invalid
Status in NUnit V2 Test Framework:
  Invalid

Bug description:
  CategoryAttribute should not accept categories containing any of the special characters
  used in category expressions: +, -, |, ( or ). An exception should be thrown in the
  consructor if an invalid category name is detected.

  Original Description:

  Version: 2.5.10
  Create a test in a category that contains hyphens (in my case V_2011-Sprint-k)
  Try to runs tests in this category with the console runner, e.g.
  nunit-console.exe wstestrunner.dll /nologo /nodots /labels /xml:temp.xml /include:V_2011-Sprint-k

  No tests executed, see console output below:

  ProcessModel: Default    DomainUsage: Single
  Execution Runtime: Default
  Included categories: V_2011-Sprint-k

  Tests run: 0, Errors: 0, Failures: 0, Inconclusive: 0, Time: 0.017 seconds
    Not run: 0, Invalid: 0, Ignored: 0, Skipped: 0

  Filtering by this category works OK in GUI app.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nunit-3.0/+bug/881357/+subscriptions