Thanks to everyone who came out yesterday and helped hack! We discovered
some bugs, fixed some issues, made a proper production branch for the
autopilot tests and started on the conversion to autopilot 1.3 for our
testcases. We started a pad to track the work, and you can view it here:
http://pad.ubuntu.com/CFXkuLR7Lb
On the manual side, Javier has opened bugs for the default applications
-- feel free to grab a bug and submit a testcase for it :-)
For those in the US, have a great long weekend!
Nicholas
On 05/22/2013 09:33 PM, Vasudevan Kottilil wrote:
Hi Nicholas,
I tried testing all the existing autopilot scripts from trunk on my
dev box running quantal 12.10 updated today morning after I pinged on
the irc. autopliot 1.3 was built after disabling lttng option. Based
on initial experience I guess I may have to create a guest image for
latest build and try again. This is what I got on my dev env.
both these appeared to go through
-test_firefox
-test_evince
tests that failed - RuntimeError:Unable to find Autopilot interface
-test_gedit
-test_nautilus
-test_shotwell
-test_totem
all these launched the respective apps and no further interactions.
Did not run test_fileroller - the app is not working (after system
update); can not create new archive of any type on my computer - this
has nothing to do with autopilot . I have a screen shot of error, can
post it if required.
These are the lingering questions that I have for tomorrow's meeting:
In setUp which should be used to launch target app? What is the criteria ?
The scripts currently use one of the three:
self.launch_test_application("appname")
or
self.start_app_window("appName")
or
self.mgr = ProcessManager.create("BAMF"),
self.mgr.start_app_window("appname")
From where or how can we get the IDs of child
windows/icons/buttons/labels etc? (in select_single etc)
These are used to select/click/enter text on target windows in several
test cases after getting a proxy object.
Thanks,
Vasudevan
Vasudevan Kottilil
On Wed, May 22, 2013 at 8:45 AM, Nicholas Skaggs
<[email protected] <mailto:[email protected]>>
wrote:
Ok, so it sounded like most people are going to be able to make
the quickly scheduled Hackathon. So, without further ado, tomorrow
in #ubuntu-quality from 1200 UTC to 2000 UTC we'll be hacking on
testcases. Hurray!
https://wiki.ubuntu.com/QATeam/Hackfest/20130523
Our goals are:
Re-organize the ubuntu-autopilot-tests trunk so known good tests
are separated from those that are a work in progress
Complete review of the manual testcases and bugs in
ubuntu-manual-tests
Migrate all the ubuntu-autopilot-tests testcases to autopilot 1.3
Clean up the old autopilot documentation and resource links from
autopilot 1.2 to autopilot 1.3
See everyone tomorrow!
Nicholas
--
Ubuntu-quality mailing list
[email protected]
<mailto:[email protected]>
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
--
Ubuntu-quality mailing list
[email protected]
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
