© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
e3ace39
(Get the code!)
OK, thanks for giving this the attention.
Yes, I was thinking it should be skipped - that functionally it would be like the [Explicit] attribute. When the programmer starts working on it, they could run the test explicitly and remove the [KnownBug] afterwards, or remove it before starting work, in which case they have a normal failing test on which they're working.
Running the test and expecting failure is also an option, although I'm not sure what the value of that would be. It raises the question of what to do with a test marked as [KnownBug] or [KnownFailure], but that actually succeeds - this could theoretically be flagged to the programmer, prompting them to remove the attribute, but it seems needlessly complicated...