John Whitlock

No, I don't believe there is a solution that will work for everyone. I've found @johnwchadwick's [solution](https://github.com/django-nose/django-nose/issues/180#issuecomment-67787705) to be the most reliable, and I'm using that on my own projects.

In TravisCI, the django-nose test suite with `--no-input`, so that test databases are recreated without prompts. Is this a public project? Can you link to the repository and the TravisCI...

Could you try reformatting your post? It is a bit hard to follow. https://guides.github.com/features/mastering-markdown/ The word "test" in a name is often used by nose to signal that a class...

I think you may be fighting nose with your wrapper, and should try another way to your desired result. For example, you could create a derived class of [TestResult](https://docs.python.org/2/library/unittest.html#unittest.TestResult) that...

@d33tah, I take it back. `nose` doesn't use `unittest` conventions, so this approach won't work. To do this with `nose`, I think you need to write a plugin. The [Failure...

Ah Selenium debugging. It's been a while since I've had to do that., I will probably have to start myself later this year. I'm planning on py.test for that. There...

Does this still happen in django-nose 1.4?

Thanks for checking. Django 1.7 improved database setup in 1.7, we may be able to lean on that code or learn from them.

There is a bit of magic around migrations and fixtures, and the magic is broken - see https://github.com/django-nose/django-nose/milestones/Fix%20REUSE_DB=1 and https://github.com/django-nose/django-nose/milestones/Fix%20FastFixtureTestCase for examples. It is possible that some of this code...

Does this still reproduce with django-nose 1.4? Do you have a public project that includes the bug?