Maybe it would be more helpful to directly show the messages from
test_minimal.py:
ldtp.client DEBUG launchapp('sol', [])
ldtp.client DEBUG getlastlog()
ldtp.client DEBUG getlastlog()
ldtp.client DEBUG getlastlog()
ldtp.client DEBUG getlastlog()
ldtp.client DEBUG getlastlog()
ldtp.client DEBUG waittillguiexist('frmKlondike')
ldtp.client DEBUG getlastlog()
process 1742: arguments to dbus_message_new_method_call() were
incorrect, assertion "destination == NULL ||
_dbus_check_is_valid_bus_name (destination)" failed in file
../../dbus/dbus-message.c line 1203.
This is normally a bug in some application using the D-Bus library.
process 1742: arguments to dbus_connection_send_with_reply() were
incorrect, assertion "message != NULL" failed in file
../../dbus/dbus-connection.c line 3349.
This is normally a bug in some application using the D-Bus library.
process 1742: arguments to dbus_pending_call_set_notify() were
incorrect, assertion "pending != NULL" failed in file
../../dbus/dbus-pending-call.c line 596.
This is normally a bug in some application using the D-Bus library.
process 1742: arguments to dbus_message_unref() were incorrect,
assertion "message != NULL" failed in file ../../dbus/dbus-message.c
line 1554.
This is normally a bug in some application using the D-Bus library.
** (-c:1742): WARNING **: AT-SPI: expected 2 values in states array; got 0
...
process 1742: arguments to dbus_message_new_method_call() were
incorrect, assertion "destination == NULL ||
_dbus_check_is_valid_bus_name (destination)" failed in file
../../dbus/dbus-message.c line 1203.
This is normally a bug in some application using the D-Bus library.
... *a few thousand more of those* ...
.
----------------------------------------------------------------------
Ran 1 test in 23.526s
OK
Xlib.protocol.request.QueryExtension
Xlib.protocol.request.QueryExtension
Xlib.protocol.request.QueryExtension
I could tar up the VM if anybody is interested...
Thanks
Christian
_______________________________________________
On Sun, Feb 5, 2012 at 3:51 PM, Christian Mallwitz <c mallwitz gmail com> wrote:
> Hi,
>
> I want to have a look at GUI testing for Gnome3 and came across Mago.
> After installing a fresh, vanilla Ubuntu 11.10 into a VirtualBox VM
> and waiting for the updates to finish, I did the steps below (can
> someone confirm that they are sufficient?) but received a rather large
> list on warnings from mago (see attachements). Is this normal? Is it
> normal for the most simple test to take 20 seconds?
>
> Do you have any other suggestions for GUI testing in Gnome3/Ubuntu?
>
> Ultimately, I want to do some performance testing by having a test
> script pick the lower right corner of my app window and simulate a
> circular mouse movement while measuring how often my widgets manages
> to re-render (ie. how long it takes) while moving the mouse around. Do
> you think that will be possible?
>
> Thanks
> Christian
>
> sudo apt-get -y install dconf-tools
> sudo apt-get -y install python-testtools bzr ldtp python-ldtp
> python-nose python-xlib python-imaging
>
> gconftool-2 --set --type bool /desktop/gnome/interface/accessibility true
> gsettings set org.gnome.desktop.interface toolkit-accessibility true
>
> reboot
>
> mkdir ~/workspace
> cd ~/workspace
>
> bzr branch lp:mago
> cd mago
>
> ./bin/mago tests/test_minimal.py > test_minimal.out 2>&1
> ./bin/mago tests/test_about.py > test_about.out 2>&1
http://live.gnome.org/DesktopTesting
desktop-testing-list mailing list
desktop-testing-list gnome org
http://mail.gnome.org/mailman/listinfo/desktop-testing-list