Unit Test integration, another GSoC proposal
mattr at kde.org
Wed Mar 12 12:11:58 UTC 2008
On Wednesday 12 March 2008 07:05:44 Andreas Pakulat wrote:
> On 12.03.08 10:59:55, Manuel Breugelmans wrote:
> > On Saturday 01 March 2008 01:19:16 Matt Rogers wrote:
> > > Go for it. Projects will be chosen based on how good their proposals
> > > are, so feel free to ask questions as you write your proposal
> > > --
> > > Matt
> > I compiled a kdevelop4 and ran the auto-tests :) Since there's currently
> > c++ support I suppose frameworks of other languages will have to wait. Is
> > there a feature planning available?
> As far as other languages go, Ruby and Python support are probably going
> to exist for KDevelop 4.1. Other languages are not planned so far, so
> they'll only be done when somebody starts to work on them (a parser for
> both Java and C# exists already)
> > Before writing out my full proposal I'd like to get your input on
> > functionality. This is what I had in mind:
> > - Graphical runner, selectable execution of tests
> This should integrate with the (existing, but probably still very basic)
> run interface we have currently.
> > - Stub creation
> For this you might want to port the filecreate plugin from kdevelop3.
No, actually he doesn't. He'll want to use duchain to generate stubs based on
another class. The file create plugin from kdevelop 3 is not worth porting, IM
HO, not with all the cool duchain stuff that we have.
> > - (semi-) self configuring cfr junit eclipse
> Thats really a good idea, we really need more auto-configuration in
> So, to conclude, I think the given points can make up enough work for a
> GSoC project. Especially getting a good design on the report view that
> makes it usable from future plugins that support other testing
More information about the KDevelop-devel