Testing request UBports Installer 0.5.3-beta
what to test
To help us testing, just download any package from the releases page or get the snap by running
snap install ubports-installer --beta. We need to test every package on every operating system, just use any Ubuntu Touch device supported by the Installer and and re-install it using the new installer version. Keep on reading to learn how to tell us the result, don't worry, it's easy!
An important new features for testers is that the installer can now automatically report testing results to OPEN-CUTS. If the installer runs into an error, choose the "report a bug" option to make the Installer automatically report a
FAILrun to UBports OPEN-CUTS and include a link to the run in the generated bug report on GitHub. If you have a problem that does not result in an error and you still choose to report a bug, the installer will automatically create a
WONKYrun and attach it to the report. This already lets us know what doesn't work, but we're also interested in learning what does! To enable success reports, set the
OPENCUTSenvironment variable (eg. by starting the installer with
OPENCUTS=true ubports-installerfrom the terminal). This will make the installer automatically report a
PASSrun, if the installation process completed without errors.
By default, the created runs will be reported anonymously. If you have an account, you can copy your API token and provide it to the UBports Installer using the
OPENCUTS_API_KEYenvironment variable (eg. by starting the installer with
OPENCUTS_API_KEY=<your-access-token> ubports-installerfrom the terminal). The installer will then report runs associated with your account. You can sign up for UBports OPEN-CUTS using your email address. Don't worry, it's easy!
- packages and changelog: https://github.com/ubports/ubports-installer/releases/tag/0.5.3-beta
- find out what packages still need testing: https://ubports.open-cuts.org/build/5f7d9d8f04d6b6000750aaac
- report a test manually: https://ubports.open-cuts.org/report?system=5e9d746c6346e112514cfec7&test=5e9d75406346e112514cfeca&build=5f7d9d8f04d6b6000750aaac
Testing the installer is always difficult, because of the many different cases and configurations to keep track of, so we depend on the community to help us out. Thank you for your help!