Improve test runner monitoring / events interfaces and enable external extensions

[GoogleCodeExporter]

The use-case is for situations where the user want to incorporate
extensions into the test execution lifecycle that require special
monitoring, such as by sending progress information to a remote service.

This requirement came up as part of an investigation into layering TeamCity
support on top of the standard MSBuild test runner task.

Ideas:
- Extract events into ITestRunnerEvents.
- Define an abstract base class for expressing the logic of new monitors
and loggers.  Provide them with full access to test runner events, test
lifecycle and log events, and test report events.
- Add a new parameter to TestLauncher to specify a list of
assembly-qualified type names or scripts to load.

We should consider defining a common standard for these external
extensibility interfaces.  Ideally they should support DLR-based scripted
extensions as well as compiled extensions.  They should also be usable in
combination with any test runner although some runners might expose
additional interfaces.

Original issue reported on code.google.com by jeff.br...@gmail.com on 17 Mar 2008 at 7:25

[GoogleCodeExporter]

Original comment by jeff.br...@gmail.com on 29 Jun 2009 at 8:32

• Added labels: Milestone-3.3

[GoogleCodeExporter]

Original comment by Yann.Tre...@gmail.com on 14 Jun 2011 at 5:53

• Added labels: Milestone-IdeaPool