Unit Test integration, another GSoC proposal

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

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

may
  w4 creation of test suite for QxRunner goal is 90%
coverage
june
  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
july
  w1 finish of pyUnit and wrap up of runner integration
  w2 abroad
  w3 port of class creation wizzard 
  w4 stub template creation
august
  w1 report framework with xml persistency, use of shiny new
Qt4.3 
QXmlStreamReader
  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

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On 18.03.08 12:58:28, Manuel Breugelmans wrote:
> 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 hope very much that KDevelop4 is in real alpha stage at
the end of may
(i.e. somethings that at least the devs can use).

> I should probably also state that my finals happen to
be in june.

Thats simply a fact you have to calculate in your time
schedule. Its not
like Google expects you to

a) work full-time on your GSoC project (though 20h/week are
probably a
must on average)
b) miss your finals due to GSoC
c) achieve all goals you've set upfront

Specifically for c), its not expected that all GSoC students
finish
their project completely in the timeline. And not fulfilling
all goals
doesn't mean your project has failed, whats important is
that you show
your interest in the project, get a decent amount of work
done and try
to communicate when you have problems (both with your mentor
as well as
the community of the project).

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

You may apply for multiple projects at once, if you get
picked for more
than one organization usually you as a student have the
choice (unless
one proposal is clearly not as good as the other(s)).

So to conclude: Yes I think you do have a chance of being
accepted and
if nobody else can be found I think I can do the mentoring
(given that I
currently get paid for working on test-related software).

Andreas

-- 
You'd like to do it instantaneously, but that's too slow.

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Tuesday 18 March 2008 14:19:58 Andreas Pakulat wrote:
> On 18.03.08 12:58:28, Manuel Breugelmans wrote:
> > I should probably also state that my finals happen
to be in june.
>
> Thats simply a fact you have to calculate in your time
schedule. Its not
> like Google expects you to
>
> a) work full-time on your GSoC project (though 20h/week
are probably a
> must on average)

During july and august gsoc will be my main occupation so
35ish hours a week 
seem reachable for sure. 

> b) miss your finals due to GSoC

I have no intentions to  It should
explain the uneven distribution of work 
in that timetable though.

> c) achieve all goals you've set upfront


> So to conclude: Yes I think you do have a chance of
being accepted and
> if nobody else can be found I think I can do the
mentoring (given that I
> currently get paid for working on test-related
software).

Looking forward to it, if accepted. In the mean time I'll
get familiar with 
the kdevelop codebase and brush up my Qt.


 - Manuel

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

On Tuesday 18 March 2008 14:19:58 Andreas Pakulat wrote:
> > 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.
>
> So to conclude: Yes I think you do have a chance of
being accepted and
> if nobody else can be found I think I can do the
mentoring (given that I
> currently get paid for working on test-related
software).

Application submitted! Further questions or critics welcome,
obviously.

Unfortunatly the detailed description's layout is a bit
borked, and edits are 
only possible after a comment or so it seems.


 - Manuel

> Andreas



_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel

I've been looking at the duchain doxygen. Am I right that
one of the main use 
cases is eclipse-style source annotations + stub creation
for 'orphans'? 
If so, actually implementing this would fit perfectly in my
gsoc. 

When writing code test-first you need this feature all the
time, ie grab all 
the unimplemented methods for a specific unimplemented class
and generate a 
stub. Good/bad idea?


 - Manuel

_______________________________________________
KDevelop-devel mailing list
KDevelop-develkdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinf
o/kdevelop-devel