As we discussed on irc last time, I suggest that we move the tests inside pelican.tests, to avoid some weird things when testing (like not using the right version of pelican for instance).
Also, gentoo packagers will be happier :)
avoid repeatition in the functional tests
Why is Left=False? In the original test it ran all three
Right, I've mis-read this, thanks!
Move the test suite inside pelican python module, as pelican.tests.
This pull request passes (merged 3376a48 into dfd3fca).
Considering we are putting the tests inside pelican now maybe we should make their imports fully qualified instead of relative?
ie from pelican.tests.support import unittest
from pelican.tests.support import unittest
yes, we should do that. Assigning myself.
Move the tests into pelican. Fix #500
docs/contribute.rst: Update tests/output generation for moved tests
This brings the docs back up to date after 547f8d2 (Move the tests
into pelican. Fix #500, 2013-04-06).