Vasudevan, do you have the code behind this? It's hard to help without
seeing it. However, assuming everything is correct, you might have found
a bug.
When you run into issues like this I would suggest asking the folks in
#ubuntu-autopilot to take a look.
http://webchat.freenode.net/?channels=#ubuntu-autopilot
If no one can responds, file a bug, provide a link to your code (lp
branch) and then provide the explanation you gave below. If they respond
and determine you found a bug, go ahead and file one also ;-)
You can file a bug here:
https://bugs.launchpad.net/autopilot/+filebug
Your right in that nautilus has changed since 12.10 and that it's a
troublesome application to introspect. If you really get stuck you can
consider hacking on something a little less troublesome -- just make
sure you file bugs and add it as affecting the project. Hope that helps!
Nicholas
On 06/04/2013 04:25 PM, Vasudevan Kottilil wrote:
Hi,
Here are some updates - still working on nautilus test case. It looks
as if there are several changes between nautilus in 12.10 and later
versions.
Running into issues when trying to move mouse cursor to execute right
clicks with in the child window. Tried using both move_to_object and
geometry and got these errors.
Please let me know if I am missing some steps here or possible
workarounds.
Basic scenario to create empty doc in saucy:
launch app
browse to /tmp
generate a tmp file name
move cursor to center of window
right click, select New Document/Empty Document
Loading tests from: /home/test/autopilot
Tests running...
======================================================================
ERROR: tests.test_nautilus.NautilusTests.test_create_empty_doc
----------------------------------------------------------------------
_StringException: Traceback (most recent call last):
File "/home/test/autopilot/tests/test_nautilus.py", line 72, in
test_create_empty_doc
self.mouse.move_to_object(self.app)
File "/usr/lib/python2.7/dist-packages/autopilot/input/_X11.py",
line 398, in move_to_object
raise ValueError("Object '%r' does not have any recognised
position attributes" % object_proxy)
ValueError: Object '<Window 'tmp' Xid: 23079834>' does not have any
recognised position attributes
Ran 1 test in 3.601s
FAILED (failures=1)
Loading tests from: /home/test/autopilot
Tests running...
======================================================================
ERROR: tests.test_nautilus.NautilusTests.test_create_empty_doc
----------------------------------------------------------------------
_StringException: Traceback (most recent call last):
File "/home/test/autopilot/tests/test_nautilus.py", line 73, in
test_create_empty_doc
self.wc = self.app.geometry
File "/usr/lib/python2.7/dist-packages/autopilot/process/_bamf.py",
line 464, in geometry
origin = GdkX11.X11Window.foreign_new_for_display(get_display(),
self._xid).get_origin()
File "/usr/lib/python2.7/dist-packages/gi/types.py", line 137, in
constructor
return info.invoke(cls, *args, **kwargs)
TypeError: argument display: Expected Gdk.Display, but got
Xlib.display.instance
Ran 1 test in 3.688s
FAILED (failures=1)
Thanks,
Vasudevan Kottilil
On Mon, Jun 3, 2013 at 8:07 AM, Nicholas Skaggs
<nicholas.ska...@canonical.com <mailto:nicholas.ska...@canonical.com>>
wrote:
I wanted to remind everyone we have another hackfest scheduled for
tomorrow:
https://wiki.ubuntu.com/QATeam/Hackfest/20130604
We will continue the migration to autopilot 1.3 (very close to
completion) as well as hack on some manual testcases too. In
addition, we'll be attempting to hack on ubiquity using autopilot
to perform automated installer tests. If you can't join us
specifically during the hackfest, that's ok! There is another one
scheduled for June 13th. And of course, ccontributions to the
manual or automated test repositories are welcome anytime, and
there's documentation to help you get started:
https://wiki.ubuntu.com/QATeam/ContributingTestcases
In addition I'd like to remind everyone June is our month for
classroom sessions. For those who signed up to host a class, now
is the time to slot in a date a time for your session;
https://wiki.ubuntu.com/Testing/Activities/Classroom/Saucy/.
Ideally we will have held all sessions before the end of June to
middle of July :-).
Finally, our remember our cadence testing is set to begin in just
a couple weeks on June 15th. This will mark the first week for us
actively testing saucy and it's development. To help you prepare,
ensure you have a computer (or virtual machine) setup and running
saucy to help test during the cadence week. If you wish, you can
plan to do some image testing and then utilize the installation
for the cadence testing as well :-). See this tutorial for more
information:
https://wiki.ubuntu.com/Testing/Cadence/Walkthrough
Remember now is the time for hacking on testcases, working through
new ideas and learning new things. As the cycle continues, more
and more testing will be required. Take the time now to make sure
our testing experience this cycle will be better than the last.
Happy Testing!
Nicholas
--
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
<mailto:Ubuntu-quality@lists.ubuntu.com>
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
--
Ubuntu-quality mailing list
Ubuntu-quality@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-quality
