Automation
Differences between revisions 1 and 28 (spanning 27 versions)
259
Comment:
|
858
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
<<Include(Testing/Header)>> | |
Line 2: | Line 3: |
List our test automation tools and development plans here ... | 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 5: |
* Desktop testing * ISO integrity and install testing * Upgrade testing (including GUI functionality) * Package install/remove testing |
In these pages is described the Ubuntu testing automation efforts, focusing on desktop testing, but covering hardware testing and API testing as well. |
Line 9: | Line 7: |
''To be fleshed out during Oct. 1-2 sprint.'' | * [[/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]] ||<tablestyle="width:95%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Sub-pages:'''||<<Navigation(children,1)>>|| |
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)