Can I run playwright tests on active browser window?

by active window you mean currently launched browser?

@skorp32 sure. I was actually hoping to run the tests on an already launched browser where I am going to different screens and playwirght almost runs like in watch mode and checks my DOM for a11y compliance

kind of like in-browser testing

Kind of possible but not super simple I would say, you will need to launch Chrome with remote debugging port and then in Playwright connect to browser via an endpoint https://playwright.dev/docs/api/class-browsertype#browser-type-connect-over-cdp.

@skorp32 thank you. this is awesome. but how do i open a socket/port in chrome? the way i understand browsers, each browser tab is a V8 isolate. so i would need to expose a port for the tab context or would i expose all the tabs in chrome?

Something like this I suppose https://gist.github.com/bobdobbalina/64450fb391dab3863e047295cb155410. It will expose whole browser, afterwards you should be able to manipulate tabs with Playwright api like usually.

Why not just get Playwright to do this in its own browser(s)?

I am new to DOM testing. so, to re-preface my question - I am testing for a11y compliance on about 600 views (based on workflow) - to allow Playwright in its own browser wouldn't you need to provide 600 routes (page.goto('https://playwright.dev/');)? from example.spec.js

test('has title', async ({ page }) => {
  await page.goto('https://playwright.dev/');

  // Expect a title "to contain" a substring.
  await expect(page).toHaveTitle(/Playwright/);
});

test('get started link', async ({ page }) => {
  await page.goto('https://playwright.dev/');

  // Click the get started link.
  await page.getByRole('link', { name: 'Get started' }).click();

  // Expects page to have a heading with the name of Installation.
  await expect(page.getByRole('heading', { name: 'Installation' })).toBeVisible();
});

@tphillips8117

sure, but isn't that better than manually doing it? You must have a list of pages/routes you can pass in?

sure. the idea is to split the fixes across different teams (we have 10+ teams). What you are suggesting is a centralized fix. tthat would be me and my junior dev 🙂

the idea is to get UAT (user acceptance) to raise bugs and assign by team

so what would Playwright do?

centralized, yes. But also automated and could be way less work in the long run

Sorry, changed it to "could be way less work" I can't say it would be less work for sure.

it just sounds like you're wanting to use playwright for only part of the test, but you could have it do the whole thing

"whole thing" meaning big picture? please elaborate

what am i missing?

I guess I might be misunderstanding your situation

playwright will only help identify the issues

it wont actually fix them for me

You're wanting to browse to each page manually, then run a playwright script to find issues on that page?

as a watcher. yes

I am wondering: Why not have playwright browse to each page itself, then run the test to find issues?

because our components behave differently based on the workflow they are in. we use "watchers" (in Vue they are watch OR watchEffect). they eventually render as static html but our component library is quasar and it does it own "stuff" on html elements

if quasar wasnt involved this would be a lot easier

I am not very familiar with how Quasar affects pages/locators, I would think it shouldn't matter too much though.

@ven0007 hopefully you get somewhere with this

Or work out a way to spare the user/UAT/dev having to browse to 600 pages 😄

@tphillips8117 LOL. Will keep you posted