Our end-to-end testing and monitoring platform makes it easy for developers to make sure their live app is creating the expected smart contract interactions for users. We currently provide frontend security to web3 apps by monitoring our clients' apps to make sure transactions point to the correct contracts and approvals give access to user funds as expected (e.g. protecting against frontend attacks such as what happened to Curve). The invention demonstrated in this Challenge takes testing to another level by converting text in the form of user stories into test code. It opens up test creation to non-technical stakeholders and can save companies/projects/developers significant time and money as well as help them provide a much safer and robust user experience. Many developers want to create high test coverage but don't have the time, energy, or resources to make it happen. We make it possible.
UX is severely lacking in web3. One primary reason is due to a lack of end-to-end testing. We want to make it easier for devs building on Base to provide safer and more robust experiences for their users. Our end-to-end testing and monitoring platform makes it easy for developers to make sure their live app is creating the expected smart contract interactions for users. We currently provide frontend security to web3 apps by monitoring our clients' apps to make sure transactions point to the correct contracts and approvals give access to user funds as expected (e.g. protecting against frontend attacks such as what happened to Curve). The invention demonstrated in this Challenge takes testing to another level by converting text in the form of user stories into test code. It opens up test creation to non-technical stakeholders and can save companies/projects/developers significant time and money. Many developers want to create high test coverage but don't have the time, energy, or resources to make it happen. We make it possible.
Judging Criteria Best for Blockchain (How much does this project improve the Blockchain ecosystem (e.g. giving developers better tools, driving adoption, improving the architecture, etc.) - max score of 100 Best User Experience (How easy is it for experts and amateurs to use this product/service?) - max score of 100 Best Engineering (How impressive is the technical implementation? How well is it engineered?) - we're making it possible for anyone to quickly write e2e tests, even non-technical stakeholders. Testing is extremely important, especially in web3, but overlooked by most projects/teams/orgs because it's time consuming and mundane. Highest "WOW" Factor (Did this project get you excited? Are you impressed?) - We think converting text in the form of user stories into test code is a pretty valuable invention. Most Innovative (How original, creative, novel, and useful is this project?) - With this tool, devs/non-devs don't need to learn a new testing framework or burn a bunch of time writing tests. All you need to do is write the flow you want to test for in english (or whatever language), and our model takes care of the rest.
Our end-to-end testing and monitoring platform makes it easy for developers to make sure their live app is creating the expected smart contract interactions for users. We currently provide frontend security to web3 apps by monitoring our clients' apps to make sure transactions point to the correct contracts and approvals give access to user funds as expected (e.g. protecting against frontend attacks such as what happened to Curve). The invention demonstrated in this Challenge takes testing to another level by converting text in the form of user stories into test code. It opens up test creation to non-technical stakeholders and can save companies/projects/developers significant time and money as well as help them provide a much safer and robust user experience. Many developers want to create high test coverage but don't have the time, energy, or resources to make it happen. We make it possible.
Our end-to-end testing and monitoring platform makes it easy for developers to make sure their live app is creating the expected smart contract interactions for users. We currently provide frontend security to web3 apps by monitoring our clients' apps to make sure transactions point to the correct contracts and approvals give access to user funds as expected (e.g. protecting against frontend attacks such as what happened to Curve). The invention demonstrated in this Challenge takes testing to another level by converting text in the form of user stories into test code. It opens up test creation to non-technical stakeholders and can save companies/projects/developers significant time and money as well as help them provide a much safer and robust user experience. Many developers want to create high test coverage but don't have the time, energy, or resources to make it happen. We make it possible.
Our end-to-end testing and monitoring platform makes it easy for developers to make sure their live app is creating the expected smart contract interactions for users. We currently provide frontend security to web3 apps by monitoring our clients' apps to make sure transactions point to the correct contracts and approvals give access to user funds as expected (e.g. protecting against frontend attacks such as what happened to Curve). The invention demonstrated in this Challenge takes testing to another level by converting text in the form of user stories into test code. It opens up test creation to non-technical stakeholders and can save companies/projects/developers significant time and money as well as help them provide a much safer and robust user experience. Many developers want to create high test coverage but don't have the time, energy, or resources to make it happen. We make it possible.
Our end-to-end testing and monitoring platform makes it easy for developers to make sure their live app is creating the expected smart contract interactions for users. We currently provide frontend security to web3 apps by monitoring our clients' apps to make sure transactions point to the correct contracts and approvals give access to user funds as expected (e.g. protecting against frontend attacks such as what happened to Curve). The invention demonstrated in this Challenge takes testing to another level by converting text in the form of user stories into test code. It opens up test creation to non-technical stakeholders and can save companies/projects/developers significant time and money as well as help them provide a much safer and robust user experience. We are a B2B SaaS company that accepts USDC for recurring payment. We can create a significant infrastructure business while also promoting the use of USDC for payment.
Background
End-to-end (E2E) tests check the functionality of a system by simulating real-world scenarios and interactions between different components. Developers traditionally do not write end-to-end tests because they are time-consuming and difficult to maintain.
Some reasons for this include:
Complexity: E2E tests need to simulate real-world scenarios and interactions between different components making tests difficult to write and maintain.
Time-consuming: The general rule is for every 1 hour of development, you should perform 1 hour writing tests to maintain high test coverage. This can slow down the development process, and writing tests isn’t as exciting as shipping new features.
Fragility: E2E tests are prone to breaking because they depend on the behavior of many different components such as CSS styling, third party component library dependencies and many other factors making it hard to reliably pinpoint the location of a component in the HTML DOM tree in a programmatic way. This can make it difficult to keep tests current.
Cost: E2E tests can be expensive to write and maintain, as they require a significant investment of time and resources.
For non-web3 interactions, the stakes aren’t as high if things break. Perhaps a user can’t create a new account, which leads to frustration and them never trying the app again. That’s bad for business, but that’s pretty much where it ends.
The stakes are much higher for web3 applications.
If an app’s UI doesn’t match what’s happening at the smart contract level, users may get hacked and/or lose funds (e.g. giving the wrong contract address access to their funds). Meanwhile, the app’s development team has no way to know this is happening.
To streamline an increase in test coverage, we’re developing a way for E2E tests to be created using natural language. Combined with our E2E testing framework (https://www.guardianui.com/), this will make it much easier for web3 apps to create safer and more robust experiences for users.
Here’s an example how natural language can be used to create a test:
User Story:
1. Go to https://app.uniswap.org/
2. Click on Get started button at the lower center.
3. Select the dropdown menu that says ETH at the upper right.
4. Click on the option that says Wrapped Ether.
5. Select the dropdown menu that says Select token in the middle of the screen.
6. Select the option that says Aave.
Benefits include:
Anybody can write tests, not just devs. No coding required.
Free up developers' time because not having to spend as much time writing tests.
Get higher test coverage while reducing cost
Tests are less brittle (Using referring expressions means tests won’t break when the location of a component in the HTML DOM tree changes for whatever reason.)
In the demo video, you will see a markdown file (with the user story above) being automatically converted into test code and run.