JP

I think django-nose2 would be the right place for layer support to be added. And/or maybe Such could be extended to support passing an optional TestCase class into createTests? On...

Should this and pretty printing tracebacks be options for the default reporter plugin, or (after we fix the reporter event and hooks) a second built-in reporter plugin? On Thu, Jul...

I think this is related to #80, or to the cause of #80, which is the way the generators plugin generates tests. It should work like the parameters plugin --...

What I can remember off the top of my head is that this behavior was based on how unittest2.discover works. That probably means the right fix is documenting the way...

I'd definitely take a patch, especially one with tests (probably one new test in nose2/tests/unit/test_debugger_plugin.py would cover it) and documentation.

No objection, as long as setup.py and requirements are updated to reflect that for python versions that don't include it. On Mon, Apr 15, 2013 at 3:50 PM, Tim Sampson...

I can't reproduce this. With this test module: ``` from nose2.compat import unittest class Test(unittest.TestCase): def setUp(self): print "setup!" def test_rcv_request(self): def do_rcv_fanout_test(type, function_name): print type, function_name yield do_rcv_fanout_test, "create",...

That's correct behavior, actually. The generator tests are generated as real test cases, so just like normal test case methods each one is run in a new instance of the...

Ah, I see what you're saying now. Sorry I misunderstood. That does seem like a bug. On Thu, May 9, 2013 at 12:49 PM, Shaun Crampton [email protected]: > But shouldn't...

The parameterize plugin looks like it behaves correctly, so the fix is probably to make the generator plugin work more like parameterize. Which would be a good thing anyway. On...