BTW: fix a CI bug(puppeteer/puppeteer#13196)

Ubuntu 23.10+ (or possibly other Linux distros in the future) ship an
AppArmor profile that applies to Chrome stable binaries installed at
/opt/google/chrome/chrome (the default installation path). This policy
is stored at /etc/apparmor.d/chrome. This AppArmor policy prevents
Chrome for Testing binaries downloaded by Puppeteer from using user namespaces
resulting in the No usable sandbox! error when trying to launch the
browser. For workarounds, see
https://chromium.googlesource.com/chromium/src/+/main/docs/security/apparmor-userns-restrictions.md

I wanna write a unit test for page.authenticate.

Is it possible to get json response from page?

/// <reference lib="dom" />

import { assertEquals } from "@std/assert";

import { launch } from "../mod.ts";

Deno.test("Testing authenticate", async (t) => {
  // Launch browser
  const browser = await launch();

  // Open the webpage
  const page = await browser.newPage(
    "https://httpbin.org/basic-auth/user/passwd",
  );

  // Provide credentials for HTTP authentication.
  await page.authenticate({ username: "user", password: "passwd" });

  // Get JSON response
  const response = JSON.parse(await page.content());

  // Assert JSON response
  assertEquals(response.authenticated, true);
  assertEquals(response.user, "user");

  // Close browser
  await browser.close();
});

Oops, merged it on accident. I'm going to revert the change. Could you open a new PR?

Is it possible to get json response from page?

I think your approach is probably the right way to go about it? I would test it and find out. Not entirely sure how to do that.