You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context
The major source of incompatibilities so far was with the browser runtime environment, to tackle before time next issues with local setups, can be good to increase coverage in the most elegant, automated way.
The Team proposed to consider Playwrite in our toolchain.
From the introduction it says " Playwright supports all modern rendering engines including Chromium, WebKit, and Firefox. Test on Windows, Linux, and macOS, locally or on CI, headless or headed with native mobile emulation of Google Chrome for Android and Mobile Safari."
Description
Do integrate Playwrite.
Write a confluence page to help changing configuration.
Add a Github Action to have the tests going E2E in the CI/CD
The expected outcome is that it should take care of the basic compatibility with most of the execution environment.
The text was updated successfully, but these errors were encountered:
victhorbi
changed the title
Add support to the playright examples
Add support to the playwright examples
Nov 15, 2024
I have had a quick review of our example apps and here are the results:
vite - uses hashing in real time, tx logs and get the last block (via button click). It has UI and uses mainnet.
node - console app, which shows results on console. No UI uses testnet.
next js - uses hashing in real time, tx logs but no get the last block button. It has UI and uses mainnet.
hardhat - just deploying/interacting with contracts. No UI. uses solo and testnet.
cloudflare - jsut simple example on web page (pure text)
So potential candidates for Playwright are vite and nextjs example. Another question is if we want to make existing examples consistent ? (except probably hardhat) As right now we use different chains and show some different stuff.
The Team agrees that most of the value comes from vite and next js UI capabilities, while the network of bigger interest is mainnet, since the SDK should always be aligned with that.
Context
The major source of incompatibilities so far was with the browser runtime environment, to tackle before time next issues with local setups, can be good to increase coverage in the most elegant, automated way.
The Team proposed to consider Playwrite in our toolchain.
From the introduction it says " Playwright supports all modern rendering engines including Chromium, WebKit, and Firefox. Test on Windows, Linux, and macOS, locally or on CI, headless or headed with native mobile emulation of Google Chrome for Android and Mobile Safari."
Description
The expected outcome is that it should take care of the basic compatibility with most of the execution environment.
The text was updated successfully, but these errors were encountered: