-
Notifications
You must be signed in to change notification settings - Fork 2
Expected failures #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
It looks like it is possible to define an entire class as expected failures @expand
class TestFailedStdlibNames(unittest.TestCase):
@foreach(list_of_expected_failures)
@unittest.expectedFailure
def test_package(self, name):
self._do_test(name) It should therefore be possible to create a derivative of |
Thanks for your feedback. I'll keep an eye on this issue. :-) (I am going to make a new release, though probably not very soon...) |
Hello. @jayvdb Big thanks for you contribution! I apologise for such a long inactivity -- for personal reasons I was unable to actively maintain the project, but now that will change. I hope I'll be able to answer to your ideas in the coming weeks. Best regards! |
@jayvdb I am not sure whether I understand correctly what is specified by items of Generally, I see two possible improvements here:
Did you refer to one of these two ideas? |
I was thinking of the second case, selectively indicating that a few of the cases will fail. |
In some later version (not in the 0.4.0 that is supposed to be released soon), I plan to add a possibility to specify -- per param instance -- a decorator (or multiple decorators) to be applied to the method parametrized using that param instance. It would be specified in a similar way contexts are... Something along the lines of the following: class TestFoo(...):
@foreach(
param(...),
param(...).deco(unittest.expectedFailure),
param(...)
.deco(my_custom_decorator),
.deco(unittest.skipIf(...)),
)
def test(...):
... |
There doesnt appear to be a way to declare that some units will be expected failures.
The text was updated successfully, but these errors were encountered: