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.
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.