looking for a simple way to label all tests in a TestCase with an attribute

[jnahmias]

Hello,

Possibly this exists already, but I don't seem to find how... I have a test case with a bunch of tests in it. How can mark the entire class with an attribute so I can exclude/skip it when running nose2? Something like the following (made-up) syntax:

import unittest

@attr_all(my_attr=True)
class MyTestCase(unittest.TestCase):

    def test_func0(self):
        pass

    def test_func1(self):
        pass

So that when I run python3 -m nose2 --plugin nose2.plugins.attrib -A '!my_attr' all the tests in MyTestCase are skipped.

[sirosen]

To be clear up-front: this doesn't exist today and won't be implemented as a new feature.
nose2 is "maintenance only" at this stage, and I don't really do work on it anymore (if it were critically broken for someone I could potentially help).

You should be able to write such a helper yourself pretty easily as a class decorator:

import unittest
import inspect


def mark_all_tests_slow(cls):
    test_methods = [
        v
        for k, v in vars(cls).items()
        # `isfunction`, since `ismethod` checks for *bound* methods
        if k.startswith("test_") and inspect.isfunction(v)
    ]
    for method in test_methods:
        method.slow = True
    return cls


@mark_all_tests_slow
class MyTests(unittest.TestCase):
    def test_func(self):
        pass


print(MyTests.test_func.slow)  # True

[jnahmias]

Hello @sirosen,

Thanks for your reply! On a lark, I tried the following and it seems to work:

$ cat test_class_attr.py 
import unittest

class LDAPSearchTestCase(unittest.TestCase):
    ldap = True

    def test_ldap_active_user(self):
        pass

    def test_ldap_filter(self):
        pass

    def test_ldap_search(self):
        pass

$ python3 -m nose2 --plugin nose2.plugins.attrib --attribute '!ldap' test_class_attr

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK

Did I just get lucky? If this is intended behavior, I'd be happy to submit a patch to the documentation and/or unit test.

[sirosen]

I took a few minutes this morning to look into this to see if the issue should be closed.

Setting an attribute on a test class works because attribute filtering does not target the test case class or its methods directly. Filtering is applied after test case classes are turned into a test suite, at which point the objects we're handling are instances of the test case class (which therefore inherit class attributes), rather than the original test methods.

The attrib plugin looks for attributes on the test case as well as the function to which it refers, so both methods are fully supported.

---

I'd be happy with adding documentation. I think a short example like the above is fine for this purpose.