Skip to content
Appmake
Product · Agent testing

Every app tested in a real browser.

Before anything goes live, Kalle opens your app in a real browser and uses it like a customer: it clicks, types, pays with a test card and checks the result. If something breaks, it fixes it and tests again.

marlowe-ceramics.appmake.ai/checkout
Checkout
Card
Expiry · CVC
Pay kr 620
Browser tests
Home page loads
Add a cup to the cart
Pay with a test card
Confirmation email sent
Watch a run

It uses your app like a customer would

Kalle opens a real browser, clicks through the flow, checks every result and fixes what fails before you ever see it.

marlowe-ceramics.appmake.ai/shop
Shop
Add to cart
Add to cart
Add to cart
Checkout · 5 tests
Home page loads
Add a cup to the cart
Discount code SPRING gives 15% off
Pay with a test card
Order confirmation shows
Testing in a real browser…
Coverage

What every test run checks

Kalle chooses tests from what your app does. A shop gets checkout tests, a booking site gets booking tests.

FlowsSign up, book, buy and log out, start to finish.
FormsRequired fields, wrong input and error messages.
PaymentsStripe test cards, receipts and refunds.
AccessibilityContrast, labels and keyboard use.
Screen sizesPhone, tablet and desktop layouts.
SpeedSlow pages and heavy images.
LinksEvery link and image on every page.
DataWhat you save is what you get back.
Find, fix, prove

It doesn't just report problems. It fixes them.

A real example from a test run. Kalle found the problem, fixed the code and tested again, all before publishing.

01 · Found
On phones, the cookie banner covered the Pay button.
02 · Fixed
.cookie-banner {
- bottom: 0;
+ bottom: 72px;
+ z-index: 20;
}
Kalle moved the banner above the checkout bar on small screens.
03 · Proved
The test ran again on a phone screen and passed.
From your plan

Tests written from what you asked for

Every item in your plan becomes one or more tests, so “done” means the feature really works.

Customers can buy gift cards
Buy a kr 500 gift cardPay with a gift card at checkoutBalance goes down after use
Members can book classes
Book a class with a passA full class shows the waitlist
Staff see today's orders
Staff log in and see ordersCustomers can't open /admin
Screen sizes

Tested on phone, tablet and desktop

Layouts break in different ways at different sizes, so every run checks all three.

Phone390 pxMenu opens and closesPay button is visibleText fits without scrolling sideways
Tablet768 pxTwo-column product gridImages load at the right sizeForms are easy to tap
Desktop1440 pxThree-column product gridHover states workWide images stay sharp
Reports

A report you can actually read

Every run ends with a summary in plain words. The full technical log is one click away.

All 7 tests passed. I fixed one problem first: on phones, the cookie banner covered the Pay button. I moved it above the checkout bar and tested again on a phone screen.
7 passed1 fixed3 screen sizes52 s
Release gate

If a test fails, nothing goes live

Your live app keeps running the last version that passed, while Kalle fixes the problem.

#216 of 6 passedLiveMon 09:12
#227 of 7 passedLiveTue 15:40
#231 failed: checkout on phonesNot publishedWed 11:05
#247 of 7 passed after a fixLiveWed 11:09
Your own tests

Ask for a test in plain words

Describe what must always work. Kalle writes the test and runs it with every change from then on.

New test · runs on every changeGIVENType “ida@” into the newsletter fieldWHENPress SubscribeTHENSee “Enter a valid email” and no signup saved
Questions

Questions about agent testing

No. Testing is part of every build, on every plan.

No. Payments are tested in Stripe test mode with test cards, so no money moves.

Kalle tells you what it tried and asks how you want to continue. Your live app keeps running the last version that passed.

Yes. Every test is saved with your code, and you can read the full log of every run.

Ship apps that work the first time

Every Appmake app is tested in a real browser before it goes live.