Unit Test integration, another GSoC proposal

Manuel Breugelmans mbr.nxi at gmail.com
Tue Mar 18 11:58:28 UTC 2008

On Saturday 15 March 2008 02:09:35 Andreas Pakulat wrote:
> On 15.03.08 01:31:59, Manu Breugel wrote:
> > I've written a draft proposal which can be viewed  at
> > http://fenix.cmi.ua.ac.be/~p035120/gsoc-0.1.txt
> >
> > wadayathink? parts that need more elaboration?
> Something that always helps in getting picked for SoC is having a more
> concrete idea about what has to be done and how long each step might
> take. Something like 4 weeks for creating a test-running framework, 2
> weeks for creating a test-stub-creation framework - that kind of stuff.
> It also helps people that look at the proposal to decide wether they
> think the amount of suggested work is too little, too much or just about
> right for the given time-frame.
> Andreas

I've talked a bit with the QxRunner author and came to the conclusion to use 
his library as a base. Mostly because its fully functional with selectable 
tests and so on. Plus it seems to be very well written with MVC. In fact I'll 
probably learn from it instead of making silly gui-programming mistakes. 
Maybe the extensions I write might be merged back into QxRunner.

Since the auto-configuring bussiness is too much a risk to turn into nothing 
I'll drop it. If you'r too lazy to write some build rules go use .NET or 

I roughly divide the work in 3 parts:
- Reengineering of QxRunner and integration into Kdevelop4
- Stub test template creation
- Report & coverage framework

  w4 creation of test suite for QxRunner goal is 90% coverage
  w1 integration of CppUnit's QxRunner into Kdevelop4
  w2 inclusion of QtUnit
  w3 inclusion of Check
  w4 study of boost.python and inclusion of pyUnit
  w1 finish of pyUnit and wrap up of runner integration
  w2 abroad
  w3 port of class creation wizzard 
  w4 stub template creation
  w1 report framework with xml persistency, use of shiny new Qt4.3 
  w2 coverage statistics integration through gcov and coverage.py
  20th deadline

Note that the estimated time contains full test-first which is obviously an 
upfront cost. You also have to take into account Kdevelop4's alpha stage. I 
should probably also state that my finals happen to be in june. However I 
intend to continue to work on it during september and maintain the plugin 
until KDE falls apart, ie never :)

So, do you guys think this stands a chance and is someone prepared to mentor 
me? If not I'd rather hear it now and apply for another gsoc.

[pfew, too long]

 - Manuel

More information about the KDevelop-devel mailing list