Extend nose? Generalize testosterone.

Now that I've refreshed my memory on testosterone, I don't think writing a nose plugin makes sense. In interactive mode, testosterone re-calls itself in non-interactive mode (using the subprocess module), and parses the output. In theory testosterone could be generalized to use any command-line test runner under the hood. For each test runner we would basically need:

• The command line signature that will produce a summary report
• A parser for the summary report
• The command line signature that will produce a detail report
• A parser for the detail report

In addition, we would need some interface for choosing from available test runners. I imagine we would ask this once on startup, and then save the result to ~/.testosterone.rc or something.

How do we determine which test runners are available? My first instinct is a custom conf file, but since we're trying to cure NIH here, let's see if we can use setuptools' plugin architecture. Feed back to Chad Whitacre.