Unexecuted test asserts in tests/config.py about djangocms-installer HOT 6 CLOSED

see this commit:
henning@aeca1de

and this doc about using the assertRaises with "with":
http://docs.python.org/2/library/unittest.html#unittest.TestCase.assertRaises

from djangocms-installer.

Ok, that's the road to take.
Plus, it's a case-by-case thing, because not every text error is encapsulated in an exception message.
For instance, in tests.config.TestConfig.test_invalid_choices the error is in self.stderr so the assert should be something like:

self.assertTrue(self.stderr.getvalue().find("--cms-version/-v: invalid choice: '2.6'") > -1)

In these cases, we'd need to split a single test in multiple ones (e.g.: test_invalid_project_name must be split in test_invalid_project_name_1, test_invalid_project_name_2 ... or clean the local stdout / stderrattributes after each sub-test

from djangocms-installer.

Error messages moved to stderr with #37
Thus in test_invalid_* tests assertion is against self.stderr while in test_check_install the current form is correct, provided the assertion are unindented outside the context manager scope

from djangocms-installer.

mock.patch "redirects" the default stdout / stderr to the StringIO objects, so we can actually read them and check them for correct messages (or suppress the output like in test_check_install)

from djangocms-installer.

OK! Well I've been thinkig it should work in this direction but I got something wrong, maybe checking stdout / sdterr...

If you're not already working on it, I can prepare the final fix with the adjusted asserts now

from djangocms-installer.

FYI: couldn't wait, I am at it now ;)

from djangocms-installer.