Thursday, 15 January 2015

unit testing - Django LiveServerTestCase + Nose -


I recently searched for Django LiveServerTestCase and labeled it as selenium Testing cases ( python manage.py test ). What I like about it, it runs a Selenium server in the background itself.

I want to tune Jenkins from the test cases and found it

  nosetests - with-xcoverage - with-xuyet --cover- Package = myapp --cover-erase pylint -f parseable myapp / | Unfortunately, when executing those scripts do not run the Django test server (and start the database etc.).  

What can anything to do with LiveServerTestCase to use nose is the way Djangogo will do this?

Analyze a reaction here because this question takes me to some interesting findings.

There is a situation in OP that I could sort by using

  dragon manage.py test functional_tests access_control - with coverage --cover-package = access_control - -cover-html   

In this case access_control product is the app and functional_tests is a separate app with liveServerTestCase tests. Access_control's standard deeggo unittests.

No comments:

Post a Comment