In this video· click a step to jump to it
Test recording
Kaijin — app walkthrough
66,788 ms · 8,332 pixels changed
We built this regression test for getkaijin.com — it's yours to keep, free.
Take this test with you
This is a real Playwright test, recorded against getkaijin.com. Claim it into your own workspace and re-run it on every deploy — free.
export async function test(page, baseUrl, screenshotPath, stepLogger) {
const STAMP = Date.now().toString(36);
const shot = async (n, slug) => {
await page.screenshot({ path: `${screenshotPath}-${n}-${slug}.png`, fullPage: true });
stepLogger.log(`Step ${n}: ${slug}`);
};
const dismissCookieBanner = async () => {
const btn = page.getByRole('button', { name: /accept|allow|got it|ok$/i });
if (await btn.first().isVisible({ timeout: 2000 }).catch(() => false)) {
await btn.first().click().catch(() => {});Checks run
Notes from the demo run
AI-generatedKaijin's marketing site leads with a clear hybrid-workflow pitch (import finished art, draw where needed, keep everything in one chapter) and a clean four-tier pricing table. The sign-up page smartly offers Google OAuth alongside email+password, and warns up front about CAPTCHA in embedded browsers. The authenticated Studio is a genuine creator tool: a guided 'production path' onboarding walks new creators from series title through story promise, lead character, world bible, first chapter, panel plan, and publishing checks, with a visible completion percentage.
- Guided production pathThe Studio's 'Creator Home' surfaces a numbered 5-step story path (story promise, lead character, character DNA, chapter board, release prep) with live percentage-complete tracking. This is a strong onboarding pattern for a tool this deep.
- Google OAuth on sign-upOffering Google alongside email+password (Clerk-powered) is a meaningfully lower-friction path than the email-only signups seen on most indie SaaS this batch.
- Clear format choiceThe new-series wizard's MANGA / MANHWA / WEBTOON picker upfront is a nice touch since it changes canvas orientation and reader UX downstream.
- Series-creation API rejects replayed sessionsPOST /api/studio/project/create returned 403 when the authenticated session was captured via storageState and replayed in a separate browser context, even though the same session rendered every page (including the pre-filled creation form) as fully authenticated. This suggests Clerk's dev-mode session/CSRF binding is tied to the originating browser/device fingerprint for mutating writes, not just cookie presence — worth checking if this also affects real users switching devices or browser profiles mid-session.
- Project cards are not real linksExisting series cards in the Studio project list are plain clickable divs (client-side router push) rather than <a href> elements, so opening a series doesn't work via standard link-following automation or browser 'open in new tab' — a small progressive-enhancement gap.
7 visual changes
Share this run
Proof your app is not AI slop
This test was built for getkaijin.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.




















