Automation
Differences between revisions 3 and 4
883
Comment:
|
940
|
Deletions are marked like this. | Additions are marked like this. |
Line 13: | Line 13: |
* Identify goals for Hardy * (any for Gutsy? ...) |
|
Line 16: | Line 18: |
* '''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. | * '''Ubuntu``Testing@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. |
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
- Identify goals for Hardy
- (any for Gutsy? ...)
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)