|
|
[[!tag archived]]
|
|
|
|
|
|
[[!meta title="Automated testing tools"]]
|
|
|
|
|
|
We already have [[an automated test suite|contribute/release_process/test/automated_tests]].
|
|
|
---
|
|
|
title: Automated testing tools
|
|
|
---
|
|
|
|
|
|
|
|
|
We already have [an automated test suite](https://tails.boum.org/contribute/release_process/test/automated_tests).
|
|
|
This page is about tools that could allow us to improve it.
|
|
|
|
|
|
[[!toc levels=2]]
|
|
|
|
|
|
[[_TOC_]]
|
|
|
|
|
|
|
|
|
# Tools
|
|
|
|
... | ... | @@ -44,8 +49,8 @@ This page is about tools that could allow us to improve it. |
|
|
|
|
|
* The pyatspi and Accessibility Python modules can be helpful
|
|
|
regardless of the actual tool we use. E.g. pyatspi can allow us to
|
|
|
listen for GUI events. Also see [[!debpkg gir1.2-atspi-2.0]] and
|
|
|
[[!debpkg gir1.2-wnck-3.0]].
|
|
|
listen for GUI events. Also see [gir1.2-atspi-2.0](http://packages.debian.org/gir1%2E2%2Datspi%2D2%2E0) and
|
|
|
[gir1.2-wnck-3.0](http://packages.debian.org/gir1%2E2%2Dwnck%2D3%2E0).
|
|
|
* [Accerciser](https://wiki.gnome.org/Apps/Accerciser), an interactive
|
|
|
accessibility explorer for the GNOME desktop
|
|
|
|
... | ... | @@ -62,7 +67,7 @@ LDTP is an open source testing tool that uses computer assistive |
|
|
technology (accessibility) to automate GUIs. It is (was?) used by GNOME,
|
|
|
Mozilla and others:
|
|
|
|
|
|
* [[!wikipedia Linux_Desktop_Testing_Project]]
|
|
|
* [Linux Desktop Testing Project](https://en.wikipedia.org/wiki/Linux%5FDesktop%5FTesting%5FProject)
|
|
|
* [homepage](http://ldtp.freedesktop.org/wiki/)
|
|
|
* latest upstream release (as of 2016-02-14) is 3.5, released mid-2013
|
|
|
* Debian Wheezy, Jessie and (as of 2016-02-14) Stretch have 2.3.1,
|
... | ... | @@ -84,7 +89,7 @@ Mozilla and others: |
|
|
|
|
|
## Using accessibility technologies?
|
|
|
|
|
|
[[!tails_ticket 10721]]
|
|
|
tails/tails#10721
|
|
|
|
|
|
In some cases, it could simplify some testing steps, such as anything
|
|
|
about navigating menus, that we're currently mostly avoiding since
|
... | ... | @@ -111,3 +116,4 @@ to Git. |
|
|
Some stuff won't be doable in a nice, high-level way, so likely we
|
|
|
will need, for some corner cases, lower-level access to the generation
|
|
|
of the Python code that will be sent and run.
|
|
|
|