Automation
Differences between revisions 2 and 26 (spanning 24 versions)
747
Comment:
|
1003
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
<<Include(Testing/Header)>> ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;"><<TableOfContents>>|| |
|
Line 2: | Line 4: |
''Working document for the Oct. 1-2 desktop testing sprint.'' | Testing automation is a key process in the testing efforts. It could simplify testers' lives by automating things that are to repeatable and living human effort to things that cannot be automated by a machine, like usability bugs. |
Line 4: | Line 6: |
== Agenda == | In these pages is described the Ubuntu testing automation efforts, focusing on desktop testing, but covering hardware testing and API testing as well. |
Line 6: | Line 8: |
* Desktop testing * Evaluating technologies LDTP, dogtail and Accerciser * ISO integrity and install testing * Upgrade testing (including GUI functionality) * Package install/remove testing * Hosting: Where and how do we host the automated tests? |
* [[/Roadmap|Testing Automation Roadmap]] * [[/Desktop|Desktop Testing]] 1. Status * [[/AtspiBlockers]] - List of applications with missing accessibility information * [[/PyreringHwTest]] - Discussion to align HWTest & Pyrering * [[/Resources|More resources on automated testing]] |
Line 13: | Line 15: |
== Ideas == * '''UbuntuTesting@Home:''' Present the test scripts in a way that allows people to test with them easily at home. Initially this would be a set of packages with test scripts glued together by a howto wiki page. Later we can add a GUI interface that lets users download and run tests. * '''Test reporting website: ''' A section of qa.ubuntu.com where users can upload test results. |
||<tablestyle="width:95%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Sub-pages:'''||<<Navigation(children,1)>>|| |
Contents |
Testing automation is a key process in the testing efforts. It could simplify testers' lives by automating things that are to repeatable and living human effort to things that cannot be automated by a machine, like usability bugs.
In these pages is described the Ubuntu testing automation efforts, focusing on desktop testing, but covering hardware testing and API testing as well.
- Status
/AtspiBlockers - List of applications with missing accessibility information
/PyreringHwTest - Discussion to align HWTest & Pyrering
- Status
Testing/Automation (last edited 2012-01-11 17:10:43 by business-89-133-214-90)