In this video· click a step to jump to it
Test recording
SMS Mobile API — app walkthrough
72,250 ms · 0 pixels changed · matches baseline
We built this regression test for smsmobileapi.com — it's yours to keep, free.
Take this test with you
This is a real Playwright test, recorded against smsmobileapi.com. Claim it into your own workspace and re-run it on every deploy — free.
export async function test(page, baseUrl, screenshotPath, stepLogger) {
const shot = async (n, slug) => {
await page.screenshot({ path: screenshotPath.replace('SCENARIO', `${n}-${slug}`), fullPage: true });
};
const site = baseUrl.replace(/\/$/, '');
const safeGoto = async (url) => {
const resp = await page.goto(url, { waitUntil: 'domcontentloaded', timeout: 20000 }).catch(() => null);
await page.waitForTimeout(800);
if (!resp || !resp.ok()) return false;
const bodyText = await page.locator('body').innerText().catch(() => '');Checks run
Notes from the demo run
AI-generatedSMSMobileAPI's marketing site is a dense WordPress build heavy on third-party integration badges (Zapier, GoHighLevel, Shopify, WooCommerce, Odoo, Python SDK). Signup is a lean 5-field form (email, name, country, primary interest) that lands you on a full-featured SMS/call/WhatsApp management dashboard immediately, with a 3-day free trial and no credit card. The dashboard itself is a large, feature-dense admin panel (20+ sidebar sections) covering SMS, calls, WhatsApp, contacts, campaigns, webhooks, and third-party connectors.
- Instant dashboard accessAccount ID + Account Licence login (not email/password) landed straight on a populated dashboard with zero blocking onboarding wizard or forced tutorial modal.
- Feature breadth visible without hardwareEven with no physical phone connected to the account, Stats Dashboard, Contacts, Campaigns, Call Manager, and the SMS compose UI all render fully and are independently useful to evaluate.
- Core product needs a physical phoneThe primary business mechanic (sending SMS via a connected mobile as a gateway) can't be exercised end-to-end without pairing a real Android/iOS device through the app -- an automated evaluator (or a busy prospect) can only get to the compose-draft step before hitting a hardware wall.
- CORS/analytics console noiseSeveral third-party analytics/beacon requests (cloudflareinsights.com, region1.analytics.google.com) fail or get CORS-blocked on nearly every page load; cosmetic but adds console noise that a stricter QA harness would flag.
- actual SMS send·No physical phone connected to the demo account (by design, to avoid requiring hardware pairing); compose form filled with a draft recipient+message and screenshotted instead of submitting a real send.
Share this run
Proof your app is not AI slop
This test was built for smsmobileapi.com — claim it free
One click copies the test and baseline screenshots into your own Lastest workspace. Re-run on every deploy and catch regressions before your users do — free, no card required.