Playwright automation in JavaScript

I automate after I understand the product. Manual testing finds what matters, and Playwright makes the stable parts repeatable on every release.

How I approach automation

A sample test

An illustrative check from a role-based access scenario: an agent must not be able to open the Super Admin area by typing the address directly.

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

test('agent cannot open the super admin area', async ({ page }) => {
  // log in as an agent
  await page.goto('/login');
  await page.getByLabel('Email').fill(process.env.AGENT_EMAIL);
  await page.getByLabel('Password').fill(process.env.AGENT_PASSWORD);
  await page.getByRole('button', { name: 'Log in' }).click();

  // try the restricted page directly
  await page.goto('/admin/users');
  await expect(page).not.toHaveURL(/admin\/users/);
  await expect(page.getByText('Access denied')).toBeVisible();
});

What this test shows

It logs in the way a real agent would, using labels and button names rather than fragile selectors. It then tries the restricted address and asserts two things the user would notice: they are not on the admin page, and they see an access denied message. This is the automated version of scenario RBAC-02 from my manual test cases.

Where automation fits in my work

In my Junior Quality Analyst role I build and maintain reusable Playwright automation and use it to widen coverage in regression cycles. Pair it with API checks in Postman and JMeter and the result is coverage from the interface down to the data.

Tools I use with it

JavaScript, JIRA for defects, GitHub, BrowserStack for browsers and devices, Postman and JMeter for the API and performance side.

More from my portfolio

Have something that needs breaking?

I’m open to remote QA roles.

Email meLinkedInResume (PDF)