Agent testing
Before anything goes live, Appmake uses your app in a real browser, the way a customer would, and fixes what fails.
What gets tested
Appmake writes tests from your plan. A shop gets checkout tests, a booking site gets booking tests. Every run covers:
- Full flows such as sign up, book, buy and log out
- Forms, required fields and error messages
- Payments with Stripe test cards
- Phone, tablet and desktop layouts
- Links, images and slow pages
- Basic accessibility: contrast, labels and keyboard use
Find, fix and prove
When a test fails, Appmake reads the error, fixes the code and runs the test again. You see each fix in the chat with the file and lines that changed.
If it cannot fix a problem on its own, it stops, shows you the error and asks how you want to continue.
Nothing broken goes live
Publishing waits for the tests to pass. If a test fails, your live app keeps running the last version that passed.
Ask for your own tests
Describe what must always work, in plain words. Appmake writes the test and runs it with every change from then on.
Make sure sold-out classes can't be booked,
even if someone opens the booking link directly.Tests are saved with your code in tests/, so a developer can run them with npm test.