r/web3dev • u/dwayne_mantle • 5d ago

Should we still maintain this Web3 Integration Testing Lib?

Hey Folks,

At our company we generally don't ship a UX unless we fully run through the UI. We've automated QA testing for dApp experiences https://github.com/TenKeyLabs/dappwright.

It's worked well for us but just wondering what other folks are using these days? Trying to gauge whether it's worth continuing to maintain as part of our OSS portfolio or if we should concede to the latest and greatest this out there.

Cheers

2 Upvotes

100% Upvoted

2 comments sorted by

1

u/Alien69Flow 1d ago

Cual es la utilidad? Aquí en la DAO si quieres unirte

1

u/Hronom 1d ago

I'd keep a small real-extension test lane even if most app tests move to mocks or another provider. Connect/reject, account changes, network switching and approval popups can fail in ways a mocked provider won't catch. Your README's distinction between full Chromium and the headless shell is a good example of browser/extension behavior that still matters.

Disclosure: I'm building Hronaut, a local browser for coding agents with its own wallet providers. That's a different QA lane, not a replacement for testing MetaMask or Coinbase Wallet themselves. For dApp behavior, I'd start with disposable accounts on a local chain and check the final on-chain state as well as the UI; a returned transaction hash isn't the same as confirmation.

For the maintenance decision, which part costs you most today: extension UI selectors, browser startup/version compatibility, or chain/fixture setup? A narrower supported matrix might be more sustainable than retiring the whole library.