3 title: Application Services version upgrades
4 permalink: /contributing/app-services-upgrades
7 Upgrading to a newer [version of App Services][as_version] upgrades the dependencies for multiple components, so it can be prudent to run a quick smoke test before it lands to ensure new functionality works and there are no regressions in the existing components.
9 ## Automated PR testing
11 A quick first step is to run the automated smoke test on the Android Components PR by commenting:
17 This will run the `test-ui-browser` task, which will execute on-device tests of a sample browser built against the A-S version. If it's totally broken, that should blow up.
21 The next step is to build a [local version of Android Components][local_build] against [Fenix][fenix] and test the following items:
22 - Check general storage components works by adding/editing/removing: bookmarks, history
23 - Sign-in/Sign-up for Sync
24 - QR code pairing for Sync
25 - Changing settings in “Choose what to sync” updates on desktop and vice versa
26 - Rename device and verify on desktop
27 - Sync Now button works
28 - Browse passwords, auto-fill, save new passwords, update them
30 - This needs push messaging keys, but we can test this without keys by using the “Sync Now” button
32 - Synced Tabs shows results from another device and vice versa
34 [as_version]: https://github.com/mozilla-mobile/android-components/blob/main/buildSrc/src/main/java/Dependencies.kt#L33
35 [local_build]: /contributing/testing-components-inside-app
36 [fenix]: https://github.com/mozilla-mobile/fenix