TestingDocumentation
Differences between revisions 1 and 22 (spanning 21 versions)
720
Comment:
|
1795
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
==Ubuntu Studio Testing Team== | ## page was renamed from UbuntuStudio/Testing <<Include(UbuntuStudio/Navigation/Header)>> <<Include(UbuntuStudio/Navigation/TestingSideBar)>> |
Line 3: | Line 5: |
Welcome this is the main wiki page of the Ubuntu Studio Testing team. Our group is co-ordinated through the launchpad team's mailing list at: https://launchpad.net/~ubuntustudio-testers | == Preliminary == |
Line 5: | Line 7: |
We plan, organize, and execute the testing for the upcoming release of Ubuntu Studio. This includes (but is not limited to): * [[UbuntuStudio/Testing/ISOTests|ISO Testing]] * [[UbuntuStudio/Testing/AppTests|Application Testing]] * [[UbuntuStudio/Testing/RTKernelTests|RT Kernel Testing]] * [[UbuntuStudio/Testing/ControlsTests|Ubuntu Studio Controls Testing]] * [[UbuntuStudio/Testing/BugTests|Confirming Bugs]] |
Testing team at Launchpad https://launchpad.net/~ubuntustudio-testers |
Line 12: | Line 9: |
Please feel free to join our team and subscribe to the mailing list. | * ISO testing - Catch bugs, report them, get them fixed * Desktop and Application Testing - Catch bugs, report them, get them fixed * Performance Testing - Look for parameters that affect system performance '''Possible Tools''' * [[Unity/QA/Autopilot|Autopilot]] * [[Testing/UTAH|UTAH]] * rt-tests (Debian/Ubuntu package) * Good old scripting [[UbuntuStudio/DesktopEnvironmentTesting|DesktopEnvironmentTesting]] - see which DEs are best performing == ISO Testing == * Manual [[UbuntuStudio/TestingQA-ISOImages|ISO Testing]] == Desktop and Application Testing == === When to do testing, and what to test? === Keep tabs on software updates, and assemble a list of them (this can be automated). Then, periodically, go through the items on that list. This is per application testing only. Some applications may need to be tested in combination with others. * Automated testing for making sure all applications are able to start. * Automated testing for the most common workflows (audio specifically) * Manual testing is less structured and lets you find wierder bugs '''important variables''' * Hardware (CPU, GPU, Audio device, etc) * Graphic Drivers (free vs proprietary) == Performance Testing == * Automated kernel testing with different configs used on the kernel (audio and kernel testing separately) * Automated process testing to measure impact of running services on audio performance (audio testing) * Automated rtirq testing ---- CategoryUbuntuStudio CategoryUbuntuStudioTesting |
Preliminary
Testing team at Launchpad https://launchpad.net/~ubuntustudio-testers
- ISO testing - Catch bugs, report them, get them fixed
- Desktop and Application Testing - Catch bugs, report them, get them fixed
- Performance Testing - Look for parameters that affect system performance
Possible Tools
DesktopEnvironmentTesting - see which DEs are best performing
ISO Testing
Manual ISO Testing
Desktop and Application Testing
When to do testing, and what to test?
Keep tabs on software updates, and assemble a list of them (this can be automated). Then, periodically, go through the items on that list. This is per application testing only. Some applications may need to be tested in combination with others.
- Automated testing for making sure all applications are able to start.
- Automated testing for the most common workflows (audio specifically)
- Manual testing is less structured and lets you find wierder bugs
important variables
- Hardware (CPU, GPU, Audio device, etc)
- Graphic Drivers (free vs proprietary)
Performance Testing
- Automated kernel testing with different configs used on the kernel (audio and kernel testing separately)
- Automated process testing to measure impact of running services on audio performance (audio testing)
- Automated rtirq testing
UbuntuStudio/TestingDocumentation (last edited 2015-04-26 14:46:58 by h-141-65)