TestingDocumentation

Differences between revisions 21 and 26 (spanning 5 versions)
⇤ ← Revision 21 as of 2013-05-17 02:05:19 →
Size: 1687
Editor: h-4-180
Comment:
← Revision 26 as of 2015-04-26 14:46:58 → ⇥
Size: 2071
Editor: h-141-65
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
Testing team at Launchpad https://launchpad.net/~ubuntustudio-testers Testing team at Launchpad https://launchpad.net/~ubuntustudio-testing
Line 9: Line 9:
 * 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		  * [[UbuntuStudio/Testing/ISOTesting|ISO testing]] - Catch bugs, report them, get them fixed
 * [[UbuntuStudio/Testing/ApplicationTesting|Desktop and Application Testing]] - Catch bugs, report them, get them fixed
 * [[UbuntuStudio/Testing/PerformanceTesting|Performance Testing]] - Look for parameters that affect system performance
 * [[UbuntuStudio/Testing/KernelTesting|Kernel Testing]] - Testing the kernel
Line 19: Line 20:
[[UbuntuStudio/DesktopEnvironmentTesting|DesktopEnvironmentTesting]] - see which DEs are best performing
Line 22: Line 25:

== Kernel Testing ==

[[UbuntuStudio/KernelTesting|Kernel Testing]]

Preliminary

Testing team at Launchpad https://launchpad.net/~ubuntustudio-testing

Possible Tools

  • Autopilot

  • UTAH

  • rt-tests (Debian/Ubuntu package)
  • Good old scripting

DesktopEnvironmentTesting - see which DEs are best performing

ISO Testing

Kernel Testing

Kernel 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

UbuntuStudio/TestingDocumentation (last edited 2015-04-26 14:46:58 by h-141-65)