For introspection what is the best way to figure out which id/name
corresponds to which button/icon/child window? for example - using
autopilot vis how to determine the id/name for the right side panel where
you right click inside the nautilus app to create new folder/doc etc?
Thanks.
Vasudevan Kot
Porting information is available here :
http://unity.ubuntu.com/autopilot/index.html
On Fri, Jun 7, 2013 at 5:30 PM, Samuel Gabbay wrote:
> I dont get this porting buissness
>
> Envoyé de mon iPod
>
> Le 2013-06-07 à 08:29 PM, "Vasudevan Kottilil" a
> écrit :
>
> Thanks Nicholas. Understood. Ini
Thanks Nicholas. Understood. Initially I assumed that proxy object itself
would be a handle to the main/top level window for the app that is launched.
Vasu
On Fri, Jun 7, 2013 at 3:11 PM, Nicholas Skaggs <
nicholas.ska...@canonical.com> wrote:
> Vasudeven, self.app is not an object. Have a look
Vasudeven, self.app is not an object. Have a look at some of the other
tests in the tree to see some examples of things. You use select_single
and select_multiple to grab dbus objects. Those can be moved to,
clicked, etc. Make sense?
Nicholas
On 06/06/2013 10:01 PM, Vasudevan Kottilil wrote:
Tried the changes and still seeing errors?
self.app is proxy returned from launch_test_application.
self.mouse.move_to_object(self.app)
ValueError: Object '' does not have any recognised position attributes
On Thu, Jun 6, 2013 at 2:21 PM, Vasudevan Kottilil wrote:
> Thanks Nicholas, I can see Nau
Thanks Nicholas, I can see NautilusDesktopWindow with GtkGrid, GtkPaned and
NautilusToolbar objects under that. Let me give it a try and get back to
you. Testcase for connecting to server will be challenging...
Vasu
Vasudevan Kottilil
On Thu, Jun 6, 2013 at 2:04 PM, Nicholas Skaggs <
nicholas.ska.
Vasudevan, the autopilot folks have a solution for us. Check this out:
http://pastebin.ubuntu.com/5740039/
Basically if we close down nautilus using the "nautilus -q" command
first, we can introspect nautilus. So this works for example:
nautilus -q
autopilot launch nautilus
autopilot vis
See
Vasudevan, sounds like you actually have everything setup properly now.
There is actually a bug in the current version of autopilot from the ppa
causing the issue you mention below. Give it another day, update and run
it again. Everything should work for you :-)
Nicholas
On 05/31/2013 03:54 A
Hi Nicholas,
Thanks - still getting errors within my dev env. Based on brief
conversation earlier on irc, I installed autopilot on vm from
ppa:autopilot/ppa. Is this the correct version for 1.3?
Got the latest version of test_nautilus from trunk and tried to run it 'as
is'. This is what I am gettin
Vasudevan, there is a basic nautilus testcase (very basic!) that is now
in the production branch. Can't wait to see you expand it to test more :-)
Vasudevan, sounds like you want to use a tool called testdrive:
https://wiki.ubuntu.com/UsingDevelopmentReleases
http://www.youtube.com/watch?v=JGZF
Hi Nicholas, Dan,
I am working on the nautilus script and was hoping to make some progress by
now but running into many issues(sorry, could not work during the long
weekend).
I had downloaded a daily build image for saucy-desktop-amd64.iso on 05/23
and tried to create a guest image using the follow
Hi everyone,
just thought i would give a quick update on the status of porting the
autopilot test cases since the last hackfest (check out the notes
http://pad.ubuntu.com/CFXkuLR7Lb) and what is working/needs reviewing
and testing.
*Firefox: *nskaggs completed this and is now merged to the p
12 matches
Mail list logo
