However this layer can be easily re-purposed to provide a flexible api for automated scripts to access the desktop as well. The layer is provided by Orca and is more commonly used for assisted access to the desktop. The most robust method for accessing the gnome desktop is through the Accessibility Layer. The first step for building an automation effort is to decide on a solid foundation. The idea is to leverage the coding potential of our internal and community QA teams to build a better product for all. We here at Canonical have begun a concerted effort to develop a framework of automated tests based on proven technologies. Today this practice is gaining a footing in the open source world as well. It is now common for QA departments to have several staff members dedicated to scripting automated tests, and basing the majority of their test effort on execution of these scripts. However, in recent years the effort to automate testing has moved this practice into the mainstream.
This is done on a more common basis with simple shell scripts when developers want to check small bits of code against it's intended feature set. In general automation is a process of using software to run a series of actions against another piece of code. The following is a brief primer on the current desktop automation efforts as well as links to resources and ideas on how you can get involved. Some of the areas discussed were tools, team collaboration, best practices, and roadblocks. Various representatives of Canonical QA have gathered in Oxford to collaborate on automating the Ubuntu desktop testing effort. Greetings from the Canonical QA Desktop Automation Sprint in Oxford UK!
0 kommentar(er)
