python -m testtools.run discover -v doesn't set verbosity
Bug #872906 reported by
John A Meinel
This bug affects 3 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
testtools |
Triaged
|
Medium
|
Unassigned |
Bug Description
I'm trying to get the list of tests that i'm running. "discover" allows a "-v" argument, but the default implementation does nothing.
I want something like:
$ py -c "import sys; from testtools import run; import unittest; prog = run.TestProgram
This is compounded by the fact that testscenarios.
Changed in testtools: | |
importance: | Undecided → Critical |
status: | New → Triaged |
tags: | added: runner |
To post a comment you must log in.
Phwoar. I looked into this, and basically the whole thing is a mess. We advertise all of these options but essentially do nothing with any of them.
Makes me regret having testtools.run in there in the first place – the world has enough test runners and I don't see that we can add a lot of value.
Not really sure what to do about this. Options are:
* rise to the challenge, make testtools.run behave the way it says
* make testtools.run's help be more accurate, cull all of the options we don't support
* kill testtools.run entirely
Maybe there are more. Those are the ones that leap to mind now.
In any case, I don't think this bug is a release blocker. Am downgrading to medium.