Last night I had the pleasure of attending the presentation of 4 Griffith University Gold Coast Students Yukito Tsunoda, Harold Haigh, Ben Cowley & Maryam Nemati. They have been working on an OLPC Activity “NoteBoard” as part of their Industry project.
The students developed the activity based on specs supplied by Sridhar at OLPC Australia. This approach differs from some of the other OLPC Activities in that it was based on a real customer need rather than the meandering evolution that we sometimes see with some of these projects.
They did a great job and I was impressed to see how quickly they picked up Python and the Sugar environment and came up with a really nice little application that I believe kids will love.
There are some bugs, but I am sure these will be ironed out and some of the team have expressed an interest in continuing on with the application after it is given back to the OLPC community.
My only feedback for the team was that they had no automated testing, this is a definite weakness amongst a lot of the OLPC activities and I am hoping future projects will take this on board to improve quality but also create a legacy for the next set of developers that take on activities as they evolve.
I’d be interested to hear from other Sugar developer on any good techniques for automated testing - I presume unit tests can be just standard PyUnit, BDD with something like freshen, but not sure how you go about automated Functional testing of the UI part of a Sugar activity… is this just standard GTK automation?