Yes, a minimal example project that demonstrates the issue would be 
helpful. My guess is that you have a mistake in your tests that's causing 
some state to leak between them.

On Monday, September 12, 2016 at 9:36:23 AM UTC-4, ankitj...@gmail.com 
wrote:
>
> Hello,
>
> I have a Python project that is using a Selenium script to emulate a user. 
> I am running this script within a Django TestCase and I use the 
> StaticLiveServerTestCase subclass to run a live Django server in the 
> background.
>
> I have also have other Unit Tests.
>
> If I run all the tests together (The Unit Tests along with the Live Server 
> Tests) using *python manage.py test*, all the test-cases that run after 
> the Selenium/Live Server test case fail. Running the unit tests separately 
> shows no failures. It seems that the database is not reset cleanly because 
> of which the subsequent test cases cannot get the Django objects that they 
> need to test against.
>
> My situation is similar to the one described in this StackOverflow 
> question here except for one difference that I face this issue even when I 
> use django test runner.
>
> http://stackoverflow.com/questions/32998166/with-py-test-database-is-not-reset-after-liveservertestcase
>
> Is there a solution to this where I can run all the tests at once and also 
> cleanly reset the database everytime? Or should I run the selenium test and 
> the Unit tests seperately?
> (I can show the code [Github] if necessary)
>
> Thanks
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-users+unsubscr...@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-users/9d212919-4f66-4812-9b94-89f5581f0ce8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to