Roundtable: testing GUIs discussion and coordination

Registered by Steve Beattie on 2010-05-03

The QA team and the Security both need to test GUI applicatiions. This session is to dicsuss the current state of different tools: mago, sikuli, kvm-autotest, others? and to coordinate efforts between the QA team and the Security team on developing tests.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Steve Beattie
Direction:
Needs approval
Assignee:
None
Definition:
Approved
Series goal:
None
Implementation:
Informational Informational
Milestone target:
None
Started by
Ara Pulido on 2010-05-19
Completed by
Ara Pulido on 2010-05-19

Related branches

Sprints

Whiteboard

Gobby notes:

== GUI Testing ==
 * GUI testing currently depends on the accessibility layer
  * Accessibility layer is not perfect. When it is broken, GUI testing breaks
  * Keeping the accessibility layer working is a noble goal in itsef
 * Sikuli - sikuli.org
  * Works based on screenshots
  * Great idea, but very heavy and ugly framework
  * Difficult to build against Linux

There are some potential problems
 - Hard to maintain (changes of themes, different resolutions, etc.)

Autotrace is a library to have a look to (http://autotrace.sourceforge.net/)
 - Gnash is already using it

- Screencast when failures

One of the things that we need to run what we have in a daily basis. This is key.

We need a framework that allows both technologies: "pysikuli" & ldtp

Once we have something working, it will be good to have policies that if Ubuntu changes the UI, a test needs to be added

-----------------------------------------------------------
This session was a roundtable about the state of the art on GUI testing. Several action items were decided there, but they are covered in other blueprints.

(?)

Work Items