You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
assignee='https://github.com/voidspace'closed_at=<Date2009-09-13.17:28:51.822>created_at=<Date2009-09-08.20:03:48.629>labels= ['type-bug', 'library']
title='TestLoader.loadTestsFromName does not use suiteClass attribute to create TestSuite instances'updated_at=<Date2009-09-13.17:28:51.821>user='https://bugs.python.org/MarkRoddy'
The TestLoader class in unittest.py has an attribute 'suiteClass' that
is used to create instances of TestSuite object(s) in the process of
loading tests. If it is desired to subclass the TestSuite class then
consumers may set this attribute on a TestLoader object in order to
override what TestSuite class gets instantiated (a pythonic version of
the factory method pattern).
However, the loadTestsFromName() on the TestLoader class does not use
this attribute to create TestSuite instances, and instead has a hard
coded reference to the unittest.TestSuite class. This results in the
base class being created instead of a possibly desired subclass that
has been specified via this attribute.
Solution for this issue is to change the loadTestsFromName() method to
use the suiteClass attribute when creating TestSuite objects instead
using a reference to the TestSuite class. Included is a patch that
implements this behavior as well as two additional test for the
test_unittest.py file which expose this issue if run against an
unpatched version of unittest.