Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for nose (standalone and for Django) #17

Open
roadsideseb opened this issue Jul 9, 2013 · 0 comments
Open

Add support for nose (standalone and for Django) #17

roadsideseb opened this issue Jul 9, 2013 · 0 comments
Labels
enhancement New features, or improvements to existing features.

Comments

@roadsideseb
Copy link

I thought it makes sense to open an issue for this so that we can keep track of progress and discussion points.

I finally managed to get a POC discoverer for nose up and running which means it is not far of. It looks like there'll be enough overlap between the generic and Django-specific nose runner to work on both simultaneously. One slight annoyance, however, will be that for Django + nose, we'll need to have a separate Discoverer that is used in place of the existing one. There's two ways of handling that:

  1. Check in the discover_commandline of DjangoProject for the used test runner in settings and switch between the default or nose one
  2. Have a separate project in cricket.django.nose that overrides DjangoProject where appropriate.

There might also be alternatives to those two that I don't see. I personally think that 2. is the more appealing solution. What are your thought?

I'll update here and attach a PR as soon as I get a first version hammered out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New features, or improvements to existing features.
Projects
None yet
Development

No branches or pull requests

1 participant