Playwright smoke test for auth flow

8916 views

                  import { test, expect } from '@playwright/test';

test('login and see dashboard', async ({ page }) => {
  await page.goto('/login');
  await page.getByTestId('email').fill('demo@example.com');
  await page.getByTestId('password').fill('password123');
  await page.getByTestId('submit').click();
  await expect(page).toHaveURL(/dashboard/);
});

When auth breaks in the UI, it’s expensive and it always seems to happen at the worst time. I keep one or two Playwright smoke tests that cover the critical path: login, navigate, create something, logout. The goal isn’t to test every edge case; it’s to catch obvious breakages (missing env vars, broken redirects, client-side exceptions) before a deploy reaches users. I run these against a seeded environment so the data is stable, and I keep selectors resilient by leaning on data-testid instead of brittle CSS selectors. With a handful of smoke tests, I get a lot of confidence for relatively little maintenance.

Mateo Rodriguez

More from Mateo Rodriguez

Playwright smoke test for auth flow

0 Comments

More from Mateo Rodriguez