Automation
Differences between revisions 1 and 3 (spanning 2 versions)
259
Comment:
|
883
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
''Working document for the Oct. 1-2 desktop testing sprint.'' | |
Line 2: | Line 3: |
List our test automation tools and development plans here ... | == Agenda == |
Line 5: | Line 6: |
* Evaluating technologies LDTP, dogtail and Accerciser | |
Line 8: | Line 10: |
* Hosting: Where and how do we host the automated tests? * Long-term maintenance: contributing test scripts back upstream * Running select tests under profiling/debugging tools like valgrind |
|
Line 9: | Line 14: |
''To be fleshed out during Oct. 1-2 sprint.'' | == 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. |
Working document for the Oct. 1-2 desktop testing sprint.
Agenda
- 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?
- Long-term maintenance: contributing test scripts back upstream
- Running select tests under profiling/debugging tools like valgrind
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.
Testing/Automation (last edited 2012-01-11 17:10:43 by business-89-133-214-90)