There are a few unit and system tests scattered throughout the Sugar source code tree. I have some of them checked out at the office, but I do not recall where they all are at home. Personally I have been caught with a bit of a Catch-22: I need to write automation to save time doing manual tests, but I have so many manual tests to run that I have not had much time to write automation. I also have looked at Dogtail as well as a few other utilities, although I did not get as far along as Daniel did. When using the AT-SPI tree browsers included with Dogtail and a few other programs, more often than not I did not see anything. It was unclear though if I was enabling AT-SPI correctly or if Dogtail was falsely thinking that it was turned on properly. This setting differs between environments [1], and X has to be restarted to make it take effect. I may have been hampered a bit by trying to find a toolkit with a graphical browser (to find controls without inspecting source code) during the GTK2 to GTK3 transition. Although AT-SPI is not GTK-specific, I still ran into a lot of compilation/library mismatch issues. There is a ticket open about getting AT-SPI working in Sugar, although we may wish to still explore other automation methods. [2] [1] <a href="https://lists.ubuntu.com/archives/ubuntu-mozillateam-bugs/2012-January/127860.html">https://lists.ubuntu.com/archives/ubuntu-mozillateam-bugs/2012-January/127860.html</a> [2] <a href="http://bugs.sugarlabs.org/ticket/3221">http://bugs.sugarlabs.org/ticket/3221</a> <div class="gmail_quote">On Sun, Jul 1, 2012 at 3:33 AM, Daniel Narvaez <<a href="mailto:dwnarvaez@gmail.com" target="_blank">dwnarvaez@gmail.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello, in the last few days I've been experimenting with dogtail <a href="https://fedorahosted.org/dogtail/" target="_blank">https://fedorahosted.org/dogtail/</a> So far I'm using it in the buildbot to run and stop all the installed activities. <a href="http://git.sugarlabs.org/sugar-build/sugar-build/blobs/master/tests/shell.py" target="_blank">http://git.sugarlabs.org/sugar-build/sugar-build/blobs/master/tests/shell.py</a> It's quite promising but apparently a bit buggy. Hopefully I can figure out how to make it reliable enough. <div class="im"> On 1 July 2012 08:33, Sridhar Dhanapalan <<a href="mailto:sridhar@laptop.org.au">sridhar@laptop.org.au</a>> wrote: > I am keen to explore ways to improve the quality and delivery time of > code. Is there any work being done to automate testing of code? > > We recently had some university students working with us to create an > activity [1], and they were using the Robot Framework [2]. > > Sridhar > > > [1] <a href="https://dev.laptop.org.au/issues/634" target="_blank">https://dev.laptop.org.au/issues/634</a> > [2] <a href="https://code.google.com/p/robotframework/" target="_blank">https://code.google.com/p/robotframework/</a> > > > Sridhar Dhanapalan > Engineering Manager > One Laptop per Child Australia > _______________________________________________ </div>> Sugar-devel mailing list > <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> > <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> -- Daniel Narvaez _______________________________________________ Sugar-devel mailing list <a href="mailto:Sugar-devel@lists.sugarlabs.org">Sugar-devel@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/sugar-devel" target="_blank">http://lists.sugarlabs.org/listinfo/sugar-devel</a> </blockquote></div>