On 2 July 2012 12:02, Sascha Silbe wrote:
> 1. Ensuring the "accessibility" helpers are running.
>
>The test suite already enables them, but they need to actually get
>started. This is done automatically by the upstream version of
>gnome-session, but sugar-toolkit ships an ancient copy
Sridhar Dhanapalan writes:
> 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?
Yes, I've been working on this whenever I have time. We already have
a data store test suite [3-5] and a semi-automated set of test
On Sun, Jul 1, 2012 at 12:30 PM, Daniel Narvaez wrote:
> On 1 July 2012 14:31, Samuel Greenfeld wrote:
> > 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 h
On 1 July 2012 14:31, Samuel Greenfeld wrote:
> 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.
Things has changed quit
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 test
Hello,
in the last few days I've been experimenting with dogtail
https://fedorahosted.org/dogtail/
So far I'm using it in the buildbot to run and stop all the installed
activities.
http://git.sugarlabs.org/sugar-build/sugar-build/blobs/master/tests/shell.py
It's quite promising but apparently
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] https://dev.laptop.o
7 matches
Mail list logo
