nose-devs/nose — Issue #465: Plugin name conflicts go unreported
Author: jpellerin
Created: 2011-12-14 16:12:06+00:00
State: open

When adding a custom plugin with the same name as one already found by the default plugin manager, the system plugin is used without any warning to the user.

In the attached file, I implement a plugin named "Skip" that skips when "MySkipTest" is raised. Since "Skip" is a built-in plugin already, raising "MySkipTest" causes an exception. When the plugin is renamed to "MySkip", everything works fine.

Possible solution: either warn the user when a plugin conflict is detected, or prefer plugins added with ``addplugins``.

Google Code Info:
Issue #: 474
Author: sjvdw...@gmail.com
Created On: 2011-11-30T05:25:59.000Z
Closed On: