Answer

Handling 'Target page, context or browser has been closed' Error in Playwright

You might encounter an error saying "target page, context or browser has been closed" when you're trying to make an isvisible() assertion after closing and opening a new browser session in Playwright. This happens because the page or context you're referencing in the assertion is no longer valid.

When you open a new browser session or close a page in Playwright, any references to that page or context become invalid. So, if you try to perform an assertion on an element using isvisible() after closing and opening a new browser session, Playwright will throw an error because it can't find the target element in the closed or newly opened session.

To avoid this error, you need to ensure that you have a valid reference to the page or context before making any assertions. Here's how you can do it:

// Open a new browser session
const browser = await playwright.chromium.launch();
const context = await browser.newContext();
const page = await context.newPage();

// Perform some actions on the page

// Close and reopen the browser session
await browser.close();
const newBrowser = await playwright.chromium.launch();
const newContext = await newBrowser.newContext();
const newPage = await newContext.newPage();

// Check if the reference to 'page' is still valid before making assertions
if (page.isClosed()) {
  // The 'page' reference is no longer valid
  console.log("The 'page' reference is no longer valid");
} else {
  // Make assertions on elements using 'isvisible()'
  const element = await newPage.$('#myElement');
  const isVisible = await element.isvisible();
  
  // Continue with other assertions and test logic
}

By checking if page (or any other reference to a page or context) is closed before making assertions, you can avoid the "target page, context or browser has been closed" error. If the reference is closed, you can handle it accordingly and proceed with your test logic.

For more tips on handling flaky tests in Playwright, check out this blog post.