Record a journey on any website, replay it on real browser engines, and get a report your whole team can read. No test code to write.
1,000 free tokens to try · Unlimited app users · Our cloud or your own servers
We open in waves. Join early access and we'll email you when your workspace is ready.
Results for "tent"
Your details
Thanks, Harshal.
New pageOrder #10482 is confirmed
Total $612.50 · Basecamp tent 2P and 2 more
or press Ctrl+Shift+R
Chromium
Chrome
Firefox
WebKit
Edge
BraveScreens from this runfernleaf.app/orders/10482
Three tests Fernleaf Supply keeps for its store. Each one runs on every engine, and none of them needed test code.
Browser test
Search, pick the Basecamp tent 2P, fill the details, place the order and check the confirmation. Recorded once with the extension, then a check for the confirmation added in the test builder.
Fig. 2. Three of its six steps.
API test
Call the orders API, then check that order #10482 comes back for Harshal with a total of $612.50. Same canvas as the browser tests.
Fig. 3. One request and the values it checks.
Visual check
Compare the Basecamp tent 2P page with its approved baseline on all six engines, so a moved price or a broken image shows up before customers see it.
Fig. 4. Baseline and this run, side by side.
Six field entries, in the order you meet them. Each figure below works: press the buttons.
Entry 01
Open the NoCodeBI extension for Chrome, pick the app and stage, press Start recording and use the site the way a customer would. A bar on the page shows the clock, the step count and the last step. Press Stop and save, review the steps in your workspace and create the test case. You add checks in the test builder after the review.
Harshalheld backThe tab is on the starting site, so typed values are kept.
Fig. 5. The recorder keeps typed values only while the tab stays on the site it started on.
Entry 02
A recording becomes a test case of blocks on a canvas. Add API calls next to the browser steps, so one test can place an order in the page and then check it through the API.
6 blocks: 4 browser, 2 API
Fig. 6. One test that places order #10482 in the page, then checks it through the API.
Entry 03
Replay the same test on Chromium, Chrome, Firefox, WebKit, Edge and Brave. Several browsers run at once, so a full suite does not wait in line.
ChromiumrunsChromerunsFirefoxrunsWebKitrunsEdgerunsBraverunsFig. 7. Which engines run, and how many browsers run at once, on each plan.
Entry 04
A test can pass every click and still ship a page that looks wrong or that some people cannot use. Add the extra checks as blocks and they run with the steps.
WCAG 2.1 AA, audited on fernleaf.app/checkout
Product page loads · passed on both profiles · Chromium engines
Fig. 8. Three checks you add as blocks. Try each tab.
Entry 05
Every run writes itself up. Share a report for one run, a whole suite or a dashboard, and follow trends across runs to see if a path is getting shakier.
Fig. 9. Pick what the report covers and its format.
Entry 06
Start a test case or a whole suite over the API from the pipeline you already have, then read the results in the formats CI tools expect.
<testsuites name="Storefront suite"
tests="24" failures="0">
<testsuite name="Checkout path"
tests="6" failures="0">
<testcase classname="Checkout path"
name="webkit-1280x720">
</testcase>
...
</testsuite>
...
</testsuites>Fig. 10. The pipeline starts the suite and reads the results back. The values shown are an example.
Tests share the workspace with everything else you build, so the app you publish and the test that checks it live side by side.
One test minute per browser is one token. Runs are billed per second, with a 10 second minimum. That is $0.01 a minute on Starter and $0.0125 on Team.
Fig. 11. Token estimate
That is $0.45 on Starter, $0.56 on Team.
45 s × 3 browsers × 20 runs, billed per second
No. Record a journey with the browser extension and it becomes steps on a canvas. You can edit, add or remove blocks there, without code.
Yes. The extension records on your own site or any other website.
Chromium, Chrome, Firefox, WebKit, Edge and Brave. Starter runs Chromium. Team and Enterprise run every engine.
One test minute per browser is one token, billed per second with a 10 second minimum. That is $0.01 on Starter and $0.0125 on Team. The 1,000 free tokens for 14 days cover up to 60 test minutes.
Yes. Start a test case or a suite over the API and read the results as JUnit XML or JSON. You can also run on your own browser grid. CI tokens and your own grid come with Team and Enterprise.
Where to begin
Add the extension, press Start recording, walk through your checkout. Then watch it pass on six engines.
We open in waves. Join early access and we'll email you when your workspace is ready.