Hallo,
short introduction: I am going to write my master thesis in the saros
project developing a test framework for the IntelliJ plugin and combining
it with STF so that the same test cases can be used for both IDE plugins.
Currently I am looking at different possibilities for testing the IntelliJ
plugin. As the IntelliJ plugin framework only supports headless testing, I
also thought about introducing a layer just below the GUI. However, at
least for IntelliJ I would prefer headless mode to launching a full-blown
IDE. This would result in faster tests and eliminate the need to write a
STF equivalent for IntelliJ.
Regarding real GUI tests, I am fairly confident that a framework like STF
could be written for IntelliJ (I am working on a proof-of-concept test
case).
As soon as I have a more complete overview of the different testing
approaches and their limitations, I will write a more detailled mail
analyzing their pros and cons.
Christian
2014-09-16 13:50 GMT+02:00 Stefan Rossbach <srossb...@arcor.de>:
> Well and that should be implemented like ?
>
> E.G
>
> 1. Like the STF (we have some parts in the SuperBot that already
> interact with the logic directly)
> 2. Or create code that will be compiled agains Saros and then load
> through the network and run on the other side
>
> The first one will require much of premade function (like the STF
> already has in its SuperBot component), the later
> is flexible (and error prone :P )
>
> On 16.09.2014 13:41, Lutz Prechelt wrote:
> > I wrote:
> >>> this will require some way of calling BULF
> >>> operations remotely.
> > Stefan wrote:
> >> Ok that would be equivalent to run Eclipse in Headless Mode.
> > No, not headless either.
> > I was thinking of two full-blown Eclipse sessions.
> > Just that their Saros components are driven by commands
> > whispered to them through an additional network connection.
> >
> > Christian, please speak up if this makes sense to you.
> > And also if it does not.
> >
> > Lutz
> >
> >
>
>
>
> ------------------------------------------------------------------------------
> Want excitement?
> Manually upgrade your production database.
> When you want reliability, choose Perforce.
> Perforce version control. Predictably reliable.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
> _______________________________________________
> DPP-Devel mailing list
> DPP-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dpp-devel
>
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
DPP-Devel mailing list
DPP-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dpp-devel
