|Deletions are marked like this.||Additions are marked like this.|
|Line 3:||Line 3:|
|||<tablestyle="width: 30%; float: right; background-color: #e1f0f4; border-radius: 10px;"><<Include(UbuntuStudio/Navigation/TestingSideBar)>>||||<<Include(UbuntuStudio/Navigation/TestingSideBar)>>|
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
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
- Hardware (CPU, GPU, Audio device, etc)
- Graphic Drivers (free vs proprietary)
- 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