Issue 68: Eclipse Plugin: performance improvements
Status:  WontFix
Owner:
Closed:  Aug 2008
Project Member Reported by marc.es...@gmail.com, Feb 29, 2008
Currently, for every test run, whether it's a single test method or 50
tests and all their methods, the following happens:

1) run ping on facade URL to confirm connectivity
2) run "startTestRun" to get testrunkey
3) run all tests
4) run "endTestRun" to clear test cache

now, 1, 2, and 4 are all lightweight, but this does mean that if you're
running a single method, you're making 4 web service calls to do a single
test. that's dumb.

So i need to add a bit of intelligence in there to make it less onerous for
those smaller runs, particularly since the smaller runs comprise the
majority of the usage for the plugin (at least, for me).

 
Aug 6, 2008
Project Member #1 marc.es...@gmail.com
closing this for now. the plugin is quite performant and this is just gravy. ther'es
so much more to do that i should focus on.
Status: WontFix