Working with the Xubuntu quality assurance team has three main aspects, testing, triaging and filing bugs. Like any piece of software, Xubuntu needs people to track bugs, test at static points and continually test the development version. More detailed discussions of the various aspects of our quality procedures can be found at the QA contributor pages.
The Xubuntu testing infrastructure is made up of three key parts:
- Xubuntu Testers team on Launchpad, which you should join once you’ve started helping with testing
- The xubuntu-devel mailing list where further information on new packages, known bugs and much more can be gathered and where discussion about critical bugs take place
- Testing trackers for Images and Packages, with information on tests to run along with instructions how to run them
A quick note on exploratory testing, in addition to testing the images and software with predefined testing actions (static testing), community members can take part in exploratory testing as well.
- In essence, exploratory testing means running the development release and doing your daily tasks with the system and finally filing bugs when you find them. This allows Xubuntu to get a much larger spread of testing than is possible with predefined tests.
- Issues which the development team are keen to address include, in addition to normally reported issues, usability bugs, missing icons, inconsistent functionality.
We have 3 PPAs which we use regularly to test packages. These are:
- Shimmer Themes for daily builds of the Shimmer Project’s projects
- Xubuntu Staging for packages and package versions that are being prepared for inclusion in Xubuntu
- Xubuntu daily builds for daily Git and Bzr builds for packages related to Xubuntu and/or Xfce4
Installing these three PPAs means that you will be using and testing packages that developers are currently working with, this means that regressions found by you will not be present once they are released.
Testing the development versions of Xubuntu and packages in it helps keep up the every day quality. If you have spare hardware resources or are able to run a virtualized testing environment, you can help.
- Milestone Testing. Stand alone image, live session and installation testing for milestones is useful in the few days before the release.
- Daily Testing. The importance of daily image testing lies mainly in knowing that boot or installation regressions haven’t appeared. Where it appears they have, if you are able to boot with a different flavours image, this can help prove a global or local to Xubuntu issue. If unsure contact the Xubuntu team, preferably on IRC.
For releases where we are making use of the Package Tracker, calls for package testing will be made to the xubuntu-devel mailing list as required. This could be a call from QA or Developers.