implement support for interactive debugger about stestr HOT 4 OPEN

Is this basically the same thing as #14 or does it differ somehow?

from stestr.

They are clearly related but I am not sure if identical. Shortly if I could define a STESTR_STRATEGY=debug that makes it start the debugger on failure I would extremely happy.

Now if I think a little bit more there is something different. As far as I know we cannot really use the debugger when we run tests in parallel and disabling parallel run is not something we want.

Thus I think this feature could be implemented in a smart way: only if you have test failures, rerun those with debug enabled. I am aware about the small chance that they would pass when run sequentially, but we can live with this risk.

If you think these are duplicated feel free to close this one and lets move the useful feedback into one ticket.

from stestr.

I don't think they are identical. AFAICS #14 would still require you to instrument your code with pdb.set_trace(), whereas the suggestion here seems to propose automatically dropping into a debugger on test failure without having to instrument - and I think that's a worthwhile idea.

from stestr.

So I just tried to use stestr with pdbpp (which is far better than pdb) and had mixed success. A basic stestr run my.test.case fails as expected unless -n is used, and then it works OK-ish, but interactive history editing and completion is completely broken :-(

In comparison it works perfectly when running python -m testtools.run my.test.case in the exact same virtualenv. So something in stestr or subunit is screwing with the interactive terminal functionality. This is really frustrating. A partial workaround is to wrap the run via rlwrap but that only brings interactive editing/history, not completion.

from stestr.