As a team of frontend and smart contract developers, we'd often ask ourselves:

How can we make sure our frontend is creating the correct smart contract interactions and is safe for our users?

Bd @balancer | Co-Founder GuardianUI.com 

We weren't happy with those options. Especially seeing frontend hacks steal hundreds of millions of dollars directly from users.

To remedy this, we built GuardianUI. It allows you to create web3 e2e tests and continuously monitor those tests in production. We also open sourced our e2e testing framework, GuardianTest.

GuardianTest is an open source framework that extends Playwright. You can now easily write full e2e tests that include smart contract interactions. 

https://docs.guardianui.com/platform/guardiantest

https://www.npmjs.com/package/@guardianui/test?activeTab=readme

Our frontend security monitoring uses tests written with GuardianTest and continuously monitors dApps to make sure they are safe (eg detecting frontend attacks). 

https://docs.guardianui.com/platform/continuous-monitoring

Free trial signup: https://airtable.com/shr5P7WXayIw9zN1R

Storycheck converts natural language into test code using user stories written in markdown. Makes it 10x easier to write and maintain tests. 

https://docs.guardianui.com/platform/storycheck-beta

The pain of e2e testing of dApps is something we hear over and over. We try to make it painless. 

Reach out if you’d like to learn more about how we can help you and your project. 

https://www.guardianui.com/

@macbudkowski you may be interested in this update :)

@launch GuardianUI - painless end-to-end testing and monitoring for dApps

Usually, the options would be:

- Manually test in production (and spend real $ doing so)
- Blindly hope any testing we did pre-deployment continued to work in production.
- Don't test (and pray) because it was too hard and time consuming (usually this)