Test suite should warn about skipped tests

Bug #280215 reported by Andreas Hasenack on 2008-10-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Storm
Undecided
Unassigned

Bug Description

The test suite should warn somewhere whenever tests are skipped, either because of a missing python module or just because the right env var was not set.

For example, the fact that the django tests were not run is not noted at the end, nor is this considered a failure or error:
[tests/django/stores.py]
Traceback (most recent call last):
  File "/home/andreas/canonical/launchpad-storm/therve/variable-leak/tests/django/stores.py", line 25, in <module>
    from django import conf
ImportError: No module named django

Also, when postgres and mysql URIs are not exported as env vars, several tests are just skipped. This should also be noted somewhere.

James Henstridge (jamesh) wrote :

The unittest framework doesn't support statuses other than success, failure or error. So we'd either need to implement this feature ourself, or make use of a unittest extension that has already done so (e.g. Trial, or jml's testtools when it gets the feature).

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers