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

useless test output #11

Open
ryazwinski opened this issue Oct 27, 2010 · 4 comments
Open

useless test output #11

ryazwinski opened this issue Oct 27, 2010 · 4 comments
Labels

Comments

@ryazwinski
Copy link

Just installed freshen, django-sane-testing and moved my tests over from lettuce...

Getting the following (pretty much useless) output from freshen (why no feature, scenario details?) :

$ DJANGO_SETTINGS_MODULE=settings PYTHONPATH=.:.. nosetests --rednose --with-django --with-freshen -v regextensions
runTest (freshen.noseplugin.FreshenTestCase) ... passed
runTest (freshen.noseplugin.FreshenTestCase) ... passed
runTest (freshen.noseplugin.FreshenTestCase) ... passed
runTest (freshen.noseplugin.FreshenTestCase) ... passed
runTest (freshen.noseplugin.FreshenTestCase) ... passed
runTest (freshen.noseplugin.FreshenTestCase) ... passed
runTest (freshen.noseplugin.FreshenTestCase) ... passed
runTest (freshen.noseplugin.FreshenTestCase) ... passed
runTest (freshen.noseplugin.FreshenTestCase) ... passed
runTest (freshen.noseplugin.FreshenTestCase) ... passed
runTest (freshen.noseplugin.FreshenTestCase) ... passed
runTest (freshen.noseplugin.FreshenTestCase) ... passed
runTest (freshen.noseplugin.FreshenTestCase) ... passed
runTest (freshen.noseplugin.FreshenTestCase) ... passed
runTest (freshen.noseplugin.FreshenTestCase) ... skipped
runTest (freshen.noseplugin.FreshenTestCase) ... skipped
runTest (freshen.noseplugin.FreshenTestCase) ... skipped
runTest (freshen.noseplugin.FreshenTestCase) ... passed
runTest (freshen.noseplugin.FreshenTestCase) ... skipped

runTest (freshen.noseplugin.FreshenTestCase) ...

19 tests run in 12.6 seconds.
4 skipped (15 tests passed)

@ghost
Copy link

ghost commented Jun 2, 2011

I believe that this is a duplicate of #8 (where a patch has already been provided)

@rlisagor
Copy link
Owner

rlisagor commented Jun 4, 2011

This could be caused by rednose. Could you try running the tests without rednose and see whether you still see the same issue?

@dexterous
Copy link
Contributor

Methinks this is in the same spirit as #14

@dexterous
Copy link
Contributor

I think we can close this now that we have merged #35; or do we want to wait for the release?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants