id	summary	reporter	owner	description	type	status	component	version	severity	resolution	keywords	cc	stage	has_patch	needs_docs	needs_tests	needs_better_patch	easy	ui_ux
7978	Contrib.Sites doctest assumes existence of current site	evan_schulz	nobody	"django.contrib.sites.tests contains the following test checking that the get_current method throws an exception if the current record doesn't exist:

{{{
>>> s = Site.objects.get_current()
...
>>> s.delete()
>>> Site.objects.get_current()
Traceback (most recent call last):
...
DoesNotExist: Site matching query does not exist.
""""""
}}}

The problem is that the default Site record (added when the table is created) is deleted by this doctest.  This creates an inconsistency when running ""./manage.py test"" as any test cases run before the contrib.sites test case will have a valid current_site() while those that run after won't.  This can be even more confusing for someone creating test cases as running tests for an individual app (""./manage.py test myapp"") may work fine while running test cases for all apps could fail (once this sites doctest gets thrown into the mix).

Proposal: Restore the default Site record at the end of the sites doctest so that other test cases can assume the record will be there (as the sites, auth, and possibly other contrib tests already do)."		closed	Testing framework	dev		fixed	sites doctest		Unreviewed	1	0	0	0	0	0