Research how to connect E2E tests to "Keprl" wallet

[Ebazhanov]

Since we want to remove Demo wallet https://github.com/confio/tgrade-app/issues/604 we should be able to connect E2E tests to Keprl wallet

[Ebazhanov]

Why did you start looking at how to test Keprl wallet?

• We don't have integration tests or E2E tests that Keprl or Ledger will be tested
• We soon need to hide our Web Wallet from the end user. (https://github.com/confio/tgrade-app/issues/604)

What does this mean for QA? Since there are no integration or e2e tests, it means that it will be necessary to do testing manually for Kepler.

My search result: Cypress does not have a direct solution on how to test the browser extension and also does not have any related plugins https://docs.cypress.io/plugins/directory

Blocker: Without additional support, cypress can only install the desired extension without a way to manipulate the actions in that extension.

Search criteria: I focused on finding a solution exclusively on cypress because it would be easier to integrate it into an existing framework.

Useful findings: There are some other similar solutions based on metamask testing

• https://github.com/CraftAcademyLabs/cypress-metamask
• https://github.com/synthetixio/synpress In addition to Cypress, we can use other frameworks like Puppeteer, Jest...
• https://github.com/fetchai/keplr-extension/pull/24/files

[Ebazhanov]

@HannuProd, @abefernan can you please advise where we should start writing tests for Keprl wallet, thanks

[abefernan]

I see a few options:

• Try to load a Chrome extension in Cypress, and see if you can interact with it.
• Try other solutions like Playwright or Puppeteer, which apparently allow to load extensions in non-headless mode.
• Keep using demo wallet for testing and manually test Keplr after every release, before announcement. This can initially be seen as a lazy solution but at the end of the day the usefulness of tests are to make sure the changes in our code do not break the user flows. I don't anticipate any change to our code breaking Keplr. Keplr functionality will break when Keplr updates, changes some stuff, and we are not aware of it. So then we need to go to the Keplr docs and update our code. Of course it'd be useful that our testing suite fetches the latest version of Keplr and makes sure it works with our code, but I don't think it's a very big deal. For me personally it's a nice to have but not a priority.

[Ebazhanov]

Thanks for the feedback Abel, I have created follow up ticket https://github.com/confio/tgrade-app/issues/614