Add smoke tests in CI

[TalDerei]

Implement the playwright end-to-end testing framework in our CI pipeline to check against transaction building.

[grod220]

What kind of things would these test help catch that we currently don't have coverage for?

Also, Vitest comes with "browser mode" that we've used to do headless browser testing. See crypto package for an example. Ideally, we could use this.

[TalDerei]

What kind of things would these test help catch that we currently don't have coverage for?

We currently don't have any smoke-test coverage against whether a transaction can be successfully built / broadcast given a set of code changes. For instance, this would have caught #416 before being committed to main.

[turbocrime]

Also, Vitest comes with "browser mode" that we've used to do headless browser testing. See crypto package for an example. Ideally, we could use this.

we currently use the "playwright" backend of vitest browser mode for those tests.

but vitest's 'browser' mode is considered unstable, and is mostly undocumented. it supports multiple backends, but its outward-facing api is fairly limited and generic - it doesn't provide access to all of the features of each underlying backend.

notably it does not seem to consider browser extensions at all. it does provide access to 'launchOptions' of playwright as 'launch' within the browser config, so we could load an extension into the browser that way. but i can't find a single example of anyone on github actually using this config field in a meaningful way

seeing issues like vitest-dev/vitest#4918 makes me skeptical that we would have enough control

it seems like there are ways to more manually use playwright in vitest

• https://github.com/vitest-dev/vitest/tree/b1462a46561d06d477cc4cf1ba96787cb66a5cba/examples/playwright
• https://www.the-koi.com/projects/how-to-run-playwright-within-vitest/

and it seems like there is @crxjs/chrome-extension-tools a vite-plugin for exactly our use case that may be worth exploring

[turbocrime]

playwright doesn't support hash routers

[turbocrime]

#418 gave playwright a try idk

[turbocrime]

the other option is webdriverio https://webdriver.io/docs/extension-testing/web-extensions/

same problem with potentially omitted features in vitest api wrapper

[jessepinho]

I can take this on after I'm done with #422

[grod220]

We briefly chatted on this in some sync. This should be de-prioritized for a few months and kick it back to the backlog for later revisiting. Getting feature complete for mainnet is the main priority.

[jessepinho]

Ah, right — thanks for the reminder