Re: [tde-general] Brainstorm Eclipse extension points
Status: Beta
Brought to you by:
dcorbin
|
From: Samuel ]s. <sa...@Up...> - 2004-01-18 11:26:18
|
On Sun, Jan 18, 2004 at 05:30:32AM -0500, David Corbin wrote: > On Sunday 18 January 2004 04:56, trz wrote: > > Samuel ]slund wrote: > > >>Please help me come up with such a list. Here are a few examples of > > >> such: 1) When configuring JUnit Launch Configurations, they give you an > > >> automatic way, and specify a particular TestSuite. It seems like it > > >> might be nice to be able to specify some other forms of "automatic". > > > > > > Being able to specify more than one suite, in execution order would > > > solve the problem of hiding failures and give possibilites for further > > > ideas, like running acceptancetests after unittests. > > > > Maybe test failures could be notifyed with a new task instead of junit > > view, like a compilation error. > > This could help with multiple failures problem, but I think could be > > useful even for simple failures: you save and have a single place to > > check for errors. > > I think we can do that (and with existing extension points). There is one more good thing about this kind of feature. It is a step towards our own handling of testresults, which we will probably need, to be able to implement things like colloring failed testcases. I would worry a little about losing the Red/Green vissual effect. But that could be solved and keeping the state of my workbench would be nice. And we probably would be able to use <ctrl>-. <ctrl>-, to navigate testfailures just like compile problems. Is that an extensionpoint? Adding items to the "problems" cathegory in the "Tasks" list. //Samuel |