MVC separation in test plug-in
While working for the lab automated testing i realized that it is virtually impossible to listen for test results from an external plug-in.
I propose a small architectural change through which we separate test running from test reporting into separate plug-ins and implement the observer pattern (actually the eclipse extension point mechanism). This should allow any plug-in to provide view services for the test plugin by providing an extension on the exposed extension point.
I already have a working implementation for this which provides the same functionality as in r23317 but splits the test controller from the view provider. I would like some feedback on this idea before committing. The current split exposes the methods in TestRunViewPart (reset, addTestcase, addTestsuite, finish…) as the extension point interface, if we go through with this a model that abstracts from the low-level filename and descriptions is needed.
Any thoughts on this proposition?Submitted by Vlad Vergu on 11 September 2011 at 17:15
Log in to post comments