Extension Beta Testing Process Documentation

[jurevans]

It would be very useful to test the auto-update behavior of the extension store version before releasing the official version, and imperative to make this a routine part of our release process prior to mainnet. Incrementing the version specified in the manifest triggers auto-update behavior. If we submit the extension as a beta, we can test this upgrade process safely before the final release is submitted.

• Add beta build script to append the correct details needed in the manifest
• Document the process of submitting a beta release to both Chrome and Firefox
• Submit to unlisted URL, or set up team permissions
• Note that we could override the Host permissions in the manifest for this Beta build, such as the internal Namadillo demo URL that we host, Housefire & Campfire instances, & localhost. However, I think that over time we likely would want to keep this open to catch problems on any host that can connect to our extension. It potentially means a longer initial review process, though I suspect that in BETA mode, this might not be an issue.

DOCS

• Chrome: See https://developer.chrome.com/docs/webstore/cws-dashboard-distribution#publishing_a_test_version
• Firefox: TODO

NOTES

• Merged feat/1093: Extension - Allow specifying beta extension build #1094 which adds BETA_RELEASE env and webpack support (Chrome only so far)

If testing upgrade between an old commit and later commit, you can still use this webpack config:

git checkout 69e70189077a52a336965dcfd93da60c65387dbd
cd apps/extension
git checkout main -- webpack.config.js
yarn wasm:build && BETA_RELEASE=true yarn build:chrome

Chrome submission

Initial upload

Store Listing

• Build Chrome extension using BETA_RELEASE=true or yarn build:chrome:beta, and with the built Zip file (e.g., namada_keychain_beta-0.3.2.zip) upload as New Item
• Provide this description: THIS EXTENSION IS FOR BETA TESTING
• Use this for the 128x128 store icon (from @ChrisHoltDesign )
  
  This will be useful for distinguishing this from the official builds when both are installed. NOTE the name will also be different (e.g., will always end with BETA)
  See Supplying Images docs
• Use this for the Screenshot:
  

Distribution

• Payments: Free of charge
• Set visibility to Unlisted NOTE See Using Private Groups for Testing below
• Distribution: All Regions

Privacy

Suggested values:

• Single purpose description:

  This is the BETA version of the Namada Keychain, an extension that manages cryptographic keys, provides signing with these keys, and allows for easy integration into any site.
  

• Storage justification:

  This extension persists an IndexedDB database for managing user-generated cryptographic keys, with some settings values also persisted via local storage.
  

• Host permission justification:

  This extension should not be restricted to any domain.
  

• Data Usage: Absolutely nothing
• Specify this Privacy Policy URL: https://namada.net/extension

Chrome Web Store documentation

Using Private Groups for Testing

As an alternative to using Unlisted on the Privacy page, we can either:

• Specify trusted users via email, who must be signed in under that email to access the extension, or:
• Create a Google Group