Testing chrome extensions
Hey, new here, sorry if redundant.
I have an extension that my site relies on called ArConnect ( a web3 wallet on the Arweave network ), which is built with plasmo. My site is a vite-react-ts stack and uses jest as a test runner. I want to add tests the check for ability to install the extension, generate a wallet (consistently), connect, disconnect, and a variety of other things.
I was planning on using playwright + jest to do this but wanted to come ask here if there was a standard way of testing with the plasmo framework?
One of the issues im looking at right now is versioning - i want to always use the latest version because the chrome store auto updates when a new version is released. I looked at the chrome store api and its not great, so maybe using the github repo would be better (its open source) and maybe set up a webhook to trigger a gh-actions workflow to test the app with new releases of the extension, with a slack webhook to notify broken functionality or something.
Thanks!
I have an extension that my site relies on called ArConnect ( a web3 wallet on the Arweave network ), which is built with plasmo. My site is a vite-react-ts stack and uses jest as a test runner. I want to add tests the check for ability to install the extension, generate a wallet (consistently), connect, disconnect, and a variety of other things.
I was planning on using playwright + jest to do this but wanted to come ask here if there was a standard way of testing with the plasmo framework?
One of the issues im looking at right now is versioning - i want to always use the latest version because the chrome store auto updates when a new version is released. I looked at the chrome store api and its not great, so maybe using the github repo would be better (its open source) and maybe set up a webhook to trigger a gh-actions workflow to test the app with new releases of the extension, with a slack webhook to notify broken functionality or something.
Thanks!
