library code cannot tell .testr.conf is missing vs incomplete or whatever

Bug #593322 reported by Jelmer Vernooij on 2010-06-13
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

  affects testrepository

Right now testrepository will raise a ValueError if there is not
testr.conf file present when attempting to rerun. It would be nice if it
could raise a more specific exception so that callers can have different
behaviour based on the exception type (such as tribunal).

What sort of behaviour do you have in mind ?

I'd be ok with custom exceptions, but lets put them in the module
raising them generally, I don't want the big pile of exceptions bzr
has, for instance :)


Changed in testrepository:
status: New → Incomplete

I was hoping to get an exception that allowed me to tell (without looking for magic words in error messages) whether or not there was sufficient configuration to run/re-run tests.

Perhaps NoTestRunConfiguration("Unable to find a .testr.conf file") ?

(.. and +1 on not sticking all exceptions in a single module)

Changed in testrepository:
status: Incomplete → Confirmed
Robert Collins (lifeless) wrote :

Sure, ok - go right ahead.

Changed in testrepository:
status: Confirmed → Triaged
importance: Undecided → Wishlist
summary: - Raise more specific exception when .testr.conf is missing
+ library code cannot tell .testr.conf is missing vs incomplete or
+ whatever
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers