tde-general — General Discussion about Test Driven Eclipse

[tde-general] FASD project: Online survey launched

[<ben...@id...>]

Dear Open Source developer

I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate.
You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it.

With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development.


With many thanks for your participation,
Benno Luthiger


PS:
The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/.
We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list.

_______________________________________________________________________

Benno Luthiger
Swiss Federal Institute of Technology Zurich
8092 Zurich

Mail: benno.luthiger(at)id.ethz.ch
_______________________________________________________________________

Re: [tde-general] Similar plugin found

[David C. <dc...@us...>]

Thanks for finding that out.  

On Thursday 11 March 2004 04:19, Carsten Behring wrote:
> On Wednesday 10 March 2004 12:18, David Corbin wrote:
> > I had noticed that too,though I haven't given it a try. We're definately
> > going to have to re-evaluate our strategy.  Give your plugin, and this
> > one, we have the choices of 1) continuing as is, 2) folding this project
> > entirely, or 3) adopting one of the others as starting point.  From what
> > I saw, I don't think that "Continuous Testing" is a live project that is
> > likely to move on (though some may say the same about this one since I've
> > been so busy..)
>
> Hi,
> I got today a mail from the guy from "continues testing" and it seems that
> it IS quite live, and that there is a good chance, that it will be even
> included in the core JUnit/Eclipse itself.
>
> Carsten
>
> The mail:
>
> Carsten,
>
> It looks like we do have similar interests.  I'm glad you found the
> plugin useful--if you have any problems with it, or suggestions for
> future work, I'm happy to hear them.
>
> Currently, my plan, which I'm working on with several of the Eclipse
> developers, is to take what I have, and hopefully integrate it directly
> into the Eclipse JDT by June--at that point, it will be as open-source
> as the rest of Eclipse:
>
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=51292
>
> Because of the somewhat tight schedule, I'm not currently planning to
> formally convert it to an open-source project before then--however, the
> source is available from the above link.  I think that there will always
> be a need for third-party plugins outside of Eclipse offering
> cutting-edge services--one thing I could use help with is to think of
> what extension points we need to leave available to make those
> third-party plug-ins possible.
>
> I've looked through the information on the sourceforge projects.  It
> appears that the functionalities of the projects overlap--is that
> right?  I'd like to try one out; which would you suggest?  Thanks,
>
>     David Saff
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> tde-general mailing list
> tde...@li...
> https://lists.sourceforge.net/lists/listinfo/tde-general

-- 
David Corbin <dc...@us...>

Re: [tde-general] Similar plugin found

[Carsten B. <car...@gm...>]

On Wednesday 10 March 2004 12:18, David Corbin wrote:
> I had noticed that too,though I haven't given it a try. We're definately
> going to have to re-evaluate our strategy.  Give your plugin, and this one,
> we have the choices of 1) continuing as is, 2) folding this project
> entirely, or 3) adopting one of the others as starting point.  From what I
> saw, I don't think that "Continuous Testing" is a live project that is
> likely to move on (though some may say the same about this one since I've
> been so busy..)
Hi,
I got today a mail from the guy from "continues testing" and it seems that it 
IS quite live, and that there is a good chance, that it will be even included 
in the core JUnit/Eclipse itself. 

Carsten

The mail:

Carsten,

It looks like we do have similar interests.  I'm glad you found the 
plugin useful--if you have any problems with it, or suggestions for 
future work, I'm happy to hear them.

Currently, my plan, which I'm working on with several of the Eclipse 
developers, is to take what I have, and hopefully integrate it directly 
into the Eclipse JDT by June--at that point, it will be as open-source 
as the rest of Eclipse:

https://bugs.eclipse.org/bugs/show_bug.cgi?id=51292

Because of the somewhat tight schedule, I'm not currently planning to 
formally convert it to an open-source project before then--however, the 
source is available from the above link.  I think that there will always 
be a need for third-party plugins outside of Eclipse offering 
cutting-edge services--one thing I could use help with is to think of 
what extension points we need to leave available to make those 
third-party plug-ins possible.

I've looked through the information on the sourceforge projects.  It 
appears that the functionalities of the projects overlap--is that 
right?  I'd like to try one out; which would you suggest?  Thanks,

    David Saff

Re: [tde-general] Similar plugin found

[David C. <dc...@us...>]

I had noticed that too,though I haven't given it a try. We're definately going 
to have to re-evaluate our strategy.  Give your plugin, and this one, we have 
the choices of 1) continuing as is, 2) folding this project entirely, or 3) 
adopting one of the others as starting point.  From what I saw, I don't think 
that "Continuous Testing" is a live project that is likely to move on (though 
some may say the same about this one since I've been so busy..)

I have very large vision for what is needed, and while I won't say I'm 
"ego-less", I really don't care if I do it or someone else does it.  I just 
want the tools.

On Wednesday 10 March 2004 05:41, Carsten Behring wrote:
> Hi all,
>
> I got noticed that there exists already a plugin, which does similar things
> to the TDE plugin: -Automated run of the tests of a project (either by
> launching a certain launch configuration OR running all tests of a project)
> -Marking failures in source and problem lists
> -The 'priority'  (order) of whch ests are run can be configured
> -Good documentation/tutorial
>
>
> I tried it with eclipse 3.0M7 and it works nicely.
>
> The url is: http://pag.csail.mit.edu/~saff/continuoustesting.html
>
>
> Regards,
>
> Carsten
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> tde-general mailing list
> tde...@li...
> https://lists.sourceforge.net/lists/listinfo/tde-general

-- 
David Corbin <dc...@us...>

[tde-general] Similar plugin found

[Carsten B. <car...@gm...>]

Hi all,

I got noticed that there exists already a plugin, which does similar things to the TDE plugin:
-Automated run of the tests of a project (either by launching a certain launch configuration OR running all tests of a project)
-Marking failures in source and problem lists
-The 'priority'  (order) of whch ests are run can be configured
-Good documentation/tutorial


I tried it with eclipse 3.0M7 and it works nicely.

The url is: http://pag.csail.mit.edu/~saff/continuoustesting.html


Regards,

Carsten

[tde-general] ANN: Eclipse TDD plugin project created

[Carsten B. <car...@gm...>]

Hi all,

I just created a new project on sourceforge with the goal to 
create a plugin for Eclipse which supports TDD. (java only)
I announce it here because it shares some ideas with the TDE plugin.

Its source code is based on a sample plugin from the book "contributing to 
eclipse" from Erich Gamma nd Kent Back.

I made some modification to the original source and it's working quite well 
already. I will release a first version soon.

Maybe some of you want to have a look at it and get/make some ideas
or comments.

The project page is: 
http://www.carstenbehring.com/eclipseTdd/

on sourceforge:  

http://sourceforge.net/projects/eclipse-tdd/

Any feedback is welcome.

Carsten Behring

Re: [tde-general] Announcement: TDE 0.1.1

[Samuel ]s. <sa...@Up...>]

On Mon, Feb 02, 2004 at 05:37:07PM -0500, David Corbin wrote:
> Samuel ]slund wrote:
> >On that note, can we get the testrun to be parallel to program
> >execution? When I make a minor GUI change (think non-automatic
> >customer testing) I want to see the result quickly, not half a minute
> >or more later when my unittests (that I know will be green) have run.
> 
> It's not now?  You can't run the application while the tests are running?

When pressing the "run" button in the workbench files are saved and
compiled, then tests are run (they are one of the builders), then the
application is started.

//Samuel

Re: [tde-general] Announcement: TDE 0.1.1

[David C. <dc...@ma...>]

Samuel ]slund wrote:
> On Sat, Jan 31, 2004 at 08:37:26PM -0500, David Corbin wrote:
> 
>>trz wrote:
>>
>>
>>>David Corbin wrote:
>>>
>>>
>>>>>- Test suite should not appear as the last run configuration in the 
>>>>>run list. This is very annoying if you are running the whole app and 
>>>>>ctrl+f11 keeps running thread instead of your app.
>>>>
>>>>
>>>>
>>>>I'm not sure there's any viable solution to this.  It might be 
>>>>possible if we implement our own Launcher, but that's certainly a low 
>>>>priority.  I'd favor an Eclipse solution that let's you bind 
>>>>keystrokes to individual launch configurations.
>>>
>>>
>>>A trick could be to remove the configuration from the run list when it 
>>>exits, but...
>>>I agree it's not very important and it happens only if you do "half 
>>>TDD": you have some tests, but you keep testing a lot of feature by hand.
>>>What do you think about this: should tde support "half tdd" or should 
>>>it "enforce" strict test first?
>>
>>I think TDE should "support" the TDD developer, not "force" him.  But 
>>that's an ideal...
> 
> 
> On that note, can we get the testrun to be parallel to program
> execution? When I make a minor GUI change (think non-automatic
> customer testing) I want to see the result quickly, not half a minute
> or more later when my unittests (that I know will be green) have run.

It's not now?  You can't run the application while the tests are running?


> 
> //Samuel
> 
> 
> 
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> tde-general mailing list
> tde...@li...
> https://lists.sourceforge.net/lists/listinfo/tde-general
> 

[tde-general] "half TDD" was: Announcement: TDE 0.1.1

[Thomas L R. <tl...@us...>]

"Samuel ]slund" 02/01/2004 05:52 PM
> can we get the testrun to be parallel to program execution? 

What do you mean by "parallel to program execution"?

> When I make a minor GUI change (think non-automatic customer
> testing) I want to see the result quickly, not half a minute or more
> later when my unittests (that I know will be green) have run.

There should be a way to turn off or work around test mode, but, for
those of us automating our GUI tests, it should not be assumed that
running the SUT == !running our unit tests.

Re: [tde-general] Announcement: TDE 0.1.1

[Samuel ]s. <sa...@Up...>]

On Sat, Jan 31, 2004 at 08:37:26PM -0500, David Corbin wrote:
> trz wrote:
> 
> >David Corbin wrote:
> >
> >>>- Test suite should not appear as the last run configuration in the 
> >>>run list. This is very annoying if you are running the whole app and 
> >>>ctrl+f11 keeps running thread instead of your app.
> >>
> >>
> >>
> >>I'm not sure there's any viable solution to this.  It might be 
> >>possible if we implement our own Launcher, but that's certainly a low 
> >>priority.  I'd favor an Eclipse solution that let's you bind 
> >>keystrokes to individual launch configurations.
> >
> >
> >A trick could be to remove the configuration from the run list when it 
> >exits, but...
> >I agree it's not very important and it happens only if you do "half 
> >TDD": you have some tests, but you keep testing a lot of feature by hand.
> >What do you think about this: should tde support "half tdd" or should 
> >it "enforce" strict test first?
> 
> I think TDE should "support" the TDD developer, not "force" him.  But 
> that's an ideal...

On that note, can we get the testrun to be parallel to program
execution? When I make a minor GUI change (think non-automatic
customer testing) I want to see the result quickly, not half a minute
or more later when my unittests (that I know will be green) have run.

//Samuel

Re: [tde-general] Announcement: TDE 0.1.1

[David C. <dc...@ma...>]

trz wrote:

> David Corbin wrote:
>
>>> - Test suite should not appear as the last run configuration in the 
>>> run list. This is very annoying if you are running the whole app and 
>>> ctrl+f11 keeps running thread instead of your app.
>>
>>
>>
>> I'm not sure there's any viable solution to this.  It might be 
>> possible if we implement our own Launcher, but that's certainly a low 
>> priority.  I'd favor an Eclipse solution that let's you bind 
>> keystrokes to individual launch configurations.
>
>
> A trick could be to remove the configuration from the run list when it 
> exits, but...
> I agree it's not very important and it happens only if you do "half 
> TDD": you have some tests, but you keep testing a lot of feature by hand.
> What do you think about this: should tde support "half tdd" or should 
> it "enforce" strict test first?

I think TDE should "support" the TDD developer, not "force" him.  But 
that's an ideal...

Re: [tde-general] Announcement: TDE 0.1.1

[trz <lbo...@fa...>]

David Corbin wrote:
>> - Test suite should not appear as the last run configuration in the 
>> run list. This is very annoying if you are running the whole app and 
>> ctrl+f11 keeps running thread instead of your app.
> 
> 
> I'm not sure there's any viable solution to this.  It might be possible 
> if we implement our own Launcher, but that's certainly a low priority.  
> I'd favor an Eclipse solution that let's you bind keystrokes to 
> individual launch configurations.

A trick could be to remove the configuration from the run list when it 
exits, but...
I agree it's not very important and it happens only if you do "half 
TDD": you have some tests, but you keep testing a lot of feature by hand.
What do you think about this: should tde support "half tdd" or should it 
"enforce" strict test first?



Bye

Lorenzo

Re: [tde-general] Announcement: TDE 0.1.1

[David C. <dc...@ma...>]

trz wrote:

> David Corbin wrote:
> > Well, 0.1.1 is now available. (http://tde.sf.net/stable). It works 
> OK on
> > 2.1.x, but I'm having problems getting it to load on 3.0M6.
> >
>
> Hi,
> what do you think is the better way to report bugs/rfe?
> Sourceforge tracker could be used.


Definately, for both bugs and RFEs.  I think for RFE's, it would 
worthwhile to mention it on this list, and foster discussion, too.

>
> Anyway, I tryed to use the plugin for a couple of projects, here are a 
> couple of things I found (most are due to current implementation).
>
> - It's nice to save and check junit bar :)
> - Test suite should not appear as the last run configuration in the 
> run list. This is very annoying if you are running the whole app and 
> ctrl+f11 keeps running thread instead of your app.

I'm not sure there's any viable solution to this.  It might be possible 
if we implement our own Launcher, but that's certainly a low priority.  
I'd favor an Eclipse solution that let's you bind keystrokes to 
individual launch configurations.

> - Tests should not be run if there are compiler errors.

Yep.  I've thought about that too.

> - If a test suite is alredy running should be stopped and "replaced" 
> by the new one.
>
Reasonable, in some ways.  Or we could just make them run sequentially.

As a general comment, let me appologize for the lack of fixes.  
SourceForge fouled up the CVS and I'm waiting for them to fix it.  In 
the meantime, I did find and fix two bugs :)

Re: [tde-general] Announcement: TDE 0.1.1

[trz <lbo...@fa...>]

David Corbin wrote:
 > Well, 0.1.1 is now available. (http://tde.sf.net/stable). It works OK on
 > 2.1.x, but I'm having problems getting it to load on 3.0M6.
 >

Hi,
what do you think is the better way to report bugs/rfe?
Sourceforge tracker could be used.

Anyway, I tryed to use the plugin for a couple of projects, here are a 
couple of things I found (most are due to current implementation).

- It's nice to save and check junit bar :)
- Test suite should not appear as the last run configuration in the run 
list. This is very annoying if you are running the whole app and 
ctrl+f11 keeps running thread instead of your app.
- Tests should not be run if there are compiler errors.
- If a test suite is alredy running should be stopped and "replaced" by 
the new one.

Last two are due to TestRunner startup being slow. Even if run in 
background on a not very very fast machine (800mhz) it slow down things.

Bye

Lorenzo

Re: [tde-general] Announcement: TDE 0.1.1

[trz <lbo...@fa...>]

David Corbin wrote:
>>- I cannot enable tde for most projects
> 
> 
> Samuel has reported having a problem with one project, and provided a sample 
> .project file.  I'll see what I can discover.  Can you find anything in 
> common with the projects that fail, or those that succeed?

I found nothing different. I would have tryed to debug but today 
sourceforge cvs is sleeping.

This is what is did:
java persp -> new proj
     java proj->next->project name "abc"->finish
abc properties->enable tde->create
     select project abc in upper textfield
     check "all test" and select abc->ok
ok(exception)

>>. In overview, "open source" link is broken
>>. all link are opened in the right frame of the help
> 
> 
> You mean, links external to the help?
> 

Yes, like the one to the tde sourceforge project.


Bye

Lorenzo

Re: [tde-general] Brainstorm Eclipse extension points

[David C. <dc...@us...>]

On Sunday 18 January 2004 09:14, Samuel ]slund wrote:
> On Sun, Jan 18, 2004 at 08:25:53AM -0500, David Corbin wrote:
> > On Sunday 18 January 2004 06:25, Samuel ]slund wrote:
> > > I would worry a little about losing the Red/Green vissual effect.
> >
> > We could always have a green INFO marker (all tests passed), and red
> > PROBLEM marker "Test Failed"
>
> I was thinking more like turning the scrollbars red on failures.
> (Or the background of the Tasks window or the toolbar background.)
> That _will_ be noticed, without getting in the way.
>
> We could have them green during a testrun like in the standard JUnit
> testrunner and then turn back the color if the testrun finnished
> w.o. errors. But it is the Red part that provides information, turning
> green might be distracting.
>

I'm not too fond of this.  It's messing with the "Eclipse and/or Native look 
and feel".  Also, I have no idea how we would achieve it.

I'd rather write our own "JUnit-like" view that "self-activated" on failure. 

> //Samuel
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> tde-general mailing list
> tde...@li...
> https://lists.sourceforge.net/lists/listinfo/tde-general

-- 
David Corbin <dc...@us...>

Re: [tde-general] Brainstorm Eclipse extension points

[Samuel ]s. <sa...@Up...>]

On Sun, Jan 18, 2004 at 08:25:53AM -0500, David Corbin wrote:
> On Sunday 18 January 2004 06:25, Samuel ]slund wrote:
> > I would worry a little about losing the Red/Green vissual effect.
> 
> We could always have a green INFO marker (all tests passed), and red PROBLEM 
> marker "Test Failed"

I was thinking more like turning the scrollbars red on failures.
(Or the background of the Tasks window or the toolbar background.)
That _will_ be noticed, without getting in the way.

We could have them green during a testrun like in the standard JUnit
testrunner and then turn back the color if the testrun finnished
w.o. errors. But it is the Red part that provides information, turning
green might be distracting.

//Samuel

Re: [tde-general] Announcement: TDE 0.1.1

[David C. <dc...@us...>]

On Sunday 18 January 2004 05:54, trz wrote:
> David Corbin wrote:
> > Well, 0.1.1 is now available. (http://tde.sf.net/stable). It works OK on
> > 2.1.x, but I'm having problems getting it to load on 3.0M6.
>
> Hi,
> I tryed it with 2.1.2 and found this
>
> - I cannot enable tde for most projects

Samuel has reported having a problem with one project, and provided a sample 
.project file.  I'll see what I can discover.  Can you find anything in 
common with the projects that fail, or those that succeed?

<snip>

> For a few projects I was able to activate tde but I do not know if I did
> something different from others. For working projects it works correctly.
>
> - launch configuration
>
> This looks more like an eclipse problem. When editing the launch
> configuration if you choose "All Tests in Projects, Source Folder or
> Package" you have to choose a project from the upper textfield too. If
> you don't, you get an "Invalid project specified" error.
> Maybe this is correct, but the search button for "all tests ..." is not
> disabled (as for "Test class") so I expected the upper project name not
> to be required.

It is an eclipse bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=49484.  
But perhaps we should try to do something to work around it, or at least 
document a work around.


>
> - tips & trick
>
> Something like this could be added:
> "Add New TestCase to Java perspective. Window->customize
> perspective->File>New->check TestCase."

:(  Seems to that's in my Java Perspective "automatically".  I'll consider it.

>
> - help (viewed with mozilla 1.5)
>
> . In overview, "open source" link is broken
> . all link are opened in the right frame of the help

You mean, links external to the help?

> . In overview, typos in "This mailing list is >>a for<< the discussion
> of various capabilities that TDE should consider >>implmenting<<"

Thanks for all the reports.

>
> Bye
>
> Lorenzo

-- 
David Corbin <dc...@ma...>

Re: [tde-general] Brainstorm Eclipse extension points

[David C. <dc...@ma...>]

On Sunday 18 January 2004 06:25, Samuel ]slund wrote:

<snip>

>
> 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.
>

Yes.  It would also address the issue of "hiding failures" when multiple 
projects are involved.

> I would worry a little about losing the Red/Green vissual effect.

We could always have a green INFO marker (all tests passed), and red PROBLEM 
marker "Test Failed"

> 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.

It's not so much an extension point, but there is an API for adding markers, 
and it's possible to provide new marker types (which may be an extension 
point).  There's an entire article on Markers on the Eclipse site.

\
-- 
David Corbin <dc...@ma...>

Re: [tde-general] Brainstorm Eclipse extension points

[Samuel ]s. <sa...@Up...>]

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

Re: [tde-general] Announcement: TDE 0.1.1

[trz <lbo...@fa...>]

David Corbin wrote:
 > Well, 0.1.1 is now available. (http://tde.sf.net/stable). It works OK on
 > 2.1.x, but I'm having problems getting it to load on 3.0M6.
 >

Hi,
I tryed it with 2.1.2 and found this

- I cannot enable tde for most projects

When i activate the checkbox, create the launch configuration and press
ok in project properties i get this

org.eclipse.core.runtime.CoreException: Problems encountered while
setting project description.
	at
org.eclipse.core.internal.resources.Project.setDescription(Project.java:805)
	at
org.eclipse.core.internal.resources.Project.setDescription(Project.java:829)
	at
net.sourceforge.tde.jdt.core.TdeJdtNature.addNatureToProject(TdeJdtNature.java:62)
	at
net.sourceforge.tde.jdt.properties.JdtAutoTestPropertyPage.performOk(JdtAutoTestPropertyPage.java:253)
	at
org.eclipse.jface.preference.PreferencePage.performApply(PreferencePage.java:395)
	at
org.eclipse.jface.preference.PreferencePage$2.widgetSelected(PreferencePage.java:270)
...

and the builder is not added to the list and if i get back to tde
properties the checkbox is not checked.

For a few projects I was able to activate tde but I do not know if I did
something different from others. For working projects it works correctly.

- launch configuration

This looks more like an eclipse problem. When editing the launch
configuration if you choose "All Tests in Projects, Source Folder or
Package" you have to choose a project from the upper textfield too. If
you don't, you get an "Invalid project specified" error.
Maybe this is correct, but the search button for "all tests ..." is not
disabled (as for "Test class") so I expected the upper project name not
to be required.

- tips & trick

Something like this could be added:
"Add New TestCase to Java perspective. Window->customize
perspective->File>New->check TestCase."

- help (viewed with mozilla 1.5)

. In overview, "open source" link is broken
. all link are opened in the right frame of the help
. In overview, typos in "This mailing list is >>a for<< the discussion
of various capabilities that TDE should consider >>implmenting<<"



Bye

Lorenzo

Re: [tde-general] Brainstorm Eclipse extension points

[David C. <dc...@ma...>]

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).

>
>
> Bye
>
> Lorenzo
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
> _______________________________________________
> tde-general mailing list
> tde...@li...
> https://lists.sourceforge.net/lists/listinfo/tde-general

-- 
David Corbin <dc...@ma...>

Re: [tde-general] Brainstorm Eclipse extension points

[trz <lbo...@fa...>]

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.


Bye

Lorenzo

Re: [tde-general] Brainstorm Eclipse extension points

[Samuel ]s. <sa...@Up...>]

On Fri, Jan 02, 2004 at 11:22:47PM -0500, David Corbin wrote:
> On Friday 02 January 2004 19:29, Samuel ]slund wrote:
> > Combining Jester with reporting throught JUnit ?
> > That could make use of pushing failures/notes from the outside.
> 
> I'm not sure I understand.

I was thinking about using idle CPU to run "mutation tests" like Jester
for java. (jester.sourceforge.net)
The results should be reported somewhere, but it is probably better to
add some kind of TODO item.

> > Can we hide JUnit if a second testrun succedes after JUnit has been
> > poped up because of a testfailure?
> 
> I'm not sure I understand this one either.  Do you mean "collapse" the 
> FastView so it's just an icon?  Get rid of the view?

If a test fails JUnit pops up. If a following testrun succeeds whatever
was ontop before should get back on top.

> > > 2) When refactoring 'Convert Local Variable to Field", it would nice to
> > > be able to add "setUp()" as an additonal choice for initialization point.
> > > (There's an open bug about this one I think)
> >
> > There is more magic that could be done here.
> > Most of the time I would use that feature I already have one or two
> > local variables with the same name, type and instantiation in other
> > test functions. Taking that refactoring step too would be helpfull.
> 
> Do you mean, "merge two classes and extract the common parts into  a base 
> class" refactoring?  3.0 is including the ability for external refactorings 
> to be added.

That sounds realy nice, but I was thinking that when I extract something
because of duplication I'd like the duplication to be replaced too.

> > 5) A way to track which files are edited and viewed. This could make
> > "magic" for chosing the right test/production code to jump to easier.
> > (We could also add jumps as a part of the class menu in the package
> > explorer.)
> 
> I think Eclipse provides this information already.  Are you saying the logic 
> for matching prod-to-test would be dependent on what editors are open?

No, but we could possibly use that information to make it more
"dwim"/inteligent.

> > 6) Can we get dependency information from the compiler?
> > Like what was used when compiling a specific function?
> 
> 3.0 has a call tree view, but it's not bound to the compiler.  I would assume 
> static AST analysis would be able to reveal what classes are referenced 
> *fairly* easily.

I was thinking more about which parts (methods/fields) that was
accessed. That could give us some more options for finding
test/production code connections.


//Samuel

Re: [tde-general] Announcement: TDE 0.1.0

[David C. <dc...@ma...>]

I don't know, as I haven't read their book yet.

Andy Tinkham wrote:

>How does this implementation of AutoTest compare with the one in Gamma &
>Beck's Contributing to Eclipse?  I just spent the weekend typing in their
>code to start to get a handle on how to do this kind of thing, and came up
>with a bunch of todo's based on their suggestions and my own ideas for where
>to take the auto-test plugin.  I'll take a look at the 0.1.1 release and see
>where the suggestions might fit.
>
>Oh, by the way, IBM did not give us the Eclipse grant, so I won't be paid to
>work on this. I'd still like to participate as time allows, however.
>
>Andy
>
>-----Original Message-----
>From: tde...@li...
>[mailto:tde...@li...] On Behalf Of David Corbin
>Sent: Sunday, January 11, 2004 1:23 PM
>To: tde...@li...; trz
>Subject: Re: [tde-general] Announcement: TDE 0.1.0
>
>
>I swear I tested this before announcing it.  I too have the error, and I'll 
>let you know when a fix is available...
>
>On Sunday 11 January 2004 12:59, trz wrote:
>  
>
>>David Corbin wrote:
>>    
>>
>>>TDE 0.1.0 is ready for you to test (no pun intended). It can be 
>>>installed from the Eclipse install site at 
>>>http://tde.sourceforge.net/stable
>>>
>>>It has a one feature in at this point (remember: release early and 
>>>often).
>>>
>>>* AutoTest - Java Projects can be configured to automatically run 
>>>Unit Tests whenever a build happens.
>>>
>>>Please install it, try it out.  GIVE FEEDBACK.  Tell us what's 
>>>missing.
>>>Join the development of the project.
>>>      
>>>
>>Hi,
>>I tryed both with 2.1.2 and 3.0M5 but I get this exception trying to 
>>enable tde in the project properties.
>>
>>java.lang.ClassNotFoundException:  
>>net.sourceforge.tde.jdt.properties.JdtAutoTestPropertyPage
>>at  
>>org.eclipse.core.internal.boot.DelegatingURLClassLoader.loadClass(Deleg
>>atin
>>gURLClassLoader.java:866) at
>>java.lang.ClassLoader.loadClass(ClassLoader.java:235)
>>...
>>
>>I've found the file tde.java.jar being called tde-jdt-ui.jar inside 
>>net.sourceforge.tde.jdt.ui_0.1.0/plugin.xml (I suppose). Renaming the 
>>file (both versions) give this error
>>
>>java.lang.Error: Unresolved compilation problems:
>>	The import net.sourceforge.tde.jdt.core cannot be resolved
>>	The import net.sourceforge.tde.jdt.core cannot be resolved
>>	The import net.sourceforge.tde.jdt.core cannot be resolved
>>	The import net.sourceforge.tde.jdt.core cannot be resolved
>>	The import net.sourceforge.tde.jdt.core cannot be resolved
>>	The import net.sourceforge.tde.jdt.core cannot be resolved
>>	ITestConfigurationManager cannot be resolved (or is not a valid
>>    
>>
>type) 
>  
>
>>for the field JdtAutoTestPropertyPage.launchConfigManager
>>	LaunchConfigManagerAdapter cannot be resolved or is not a type
>>	ProjectAdapter cannot be resolved or is not a type
>>	ProxyBuilder cannot be resolved
>>	TdeJdtCorePlugin cannot be resolved
>>	TdeJdtCorePlugin cannot be resolved
>>	launchConfigManager cannot be resolved
>>	...
>>
>>Any idea?
>>
>>
>>Bye
>>
>>
>>Lorenzo
>>
>>
>>
>>-------------------------------------------------------
>>This SF.net email is sponsored by: Perforce Software. Perforce is the 
>>Fast Software Configuration Management System offering advanced 
>>branching capabilities and atomic changes on 50+ platforms. Free Eval! 
>>http://www.perforce.com/perforce/loadprog.html
>>_______________________________________________
>>tde-general mailing list
>>tde...@li... 
>>https://lists.sourceforge.net/lists/listinfo/tde-general
>>    
>>
>
>  
>