Jump to content

Testing Team: Difference between revisions

From postmarketOS Wiki
Add myself (Camden/Caffeine) to the testing_team.
m Fix uppercase
Line 70: Line 70:
| No accessories
| No accessories
|-
|-
| [[User:EnderNightLord|EnderNightlord]]
| [[User:EnderNightLord|EnderNightLord]]
| CarbonatedCaffeine
| CarbonatedCaffeine
| @carbonatedcaffeine:matrix.org
| @carbonatedcaffeine:matrix.org

Revision as of 23:21, 21 May 2023

The testing team allows community members to directly get involved in the testing process. When there is a shiny new thing to test, users in the table below will get a notification (usually via mention in pmaports). They can install the change and report back whether everything worked as expected, or whether there is a regression.

FAQ

Can I join the testing team?

Thank you for considering! Yes, as long as you ...

  • ... have familiarized yourself enough with pmOS that you feel comfortable testing changes
  • ... make sure you don't lose important data (make backups as needed!)

Benefits:

  • You can dramatically help improving the quality of postmarketOS for the device you are using.
  • You hold the cool new changes in your hands before everyone else!

To join the testing team, add yourself to the table of members on this wiki page.

Consider joining the release-party channel, where testing of releases and bigger changes gets coordinated.

How to test changes?

Merge requests

Install binary packages from merge request pipelines on your device with mrtest.

Releases

  • Either download an image for your device. Make sure to upgrade all packages before doing any tests.
  • Or build your own image with pmbootstrap. Make sure to select the new release in pmbootstrap init.

Service packs

We plan to have a staging repository for future service packs (build.postmarketos.org#117). Detailed instructions will be added here once implemented.

What about device maintainers?

Typically device maintainers are not part of the testing team. Device maintainers already test on their devices as good as they can, the point of the testing team is to scale testing across many people, so development can be done both faster and with less regressions.

Best practices for editing the table?

  • Keep the entries consistent, so they can be easily searched (same spelling for UI names etc).
  • What to put in "Notes":
    • Revision of your device, if there are multiple ones (e.g. PinePhone revisions)
    • The panel of the device if there are multiple ones
    • Add-ons you would like to test, such as the PinePhone hardware keyboard

Members

Wiki username GitLab username Matrix username Device codenames UIs (or any) Notes
Anjanmomi anjandev @anjan:postmarketos.org xiaomi-beryllium postmarketos-ui-sxmo-de-sway Tianma Panel
Knuxfanwin8 knuxify @knuxify:cybre.space samsung-a5
raspberry-pi4
postmarketos-ui-phosh samsung-a5: SM-A500FU
Weissnix4711 Weissnix4711 @weissnix4711:matrix.org pine64-pinephonepro postmarketos-ui-gnome-mobile No accessories
EnderNightLord CarbonatedCaffeine @carbonatedcaffeine:matrix.org pine64-pinephone
oneplus-enchilada
samsung-m0
postmarketos-ui-phosh
postmarketos-ui-plasma-mobile
N/A

See also