playwright-java VS Playwright

https://playwright.dev/java/ - Playwright is nice if you want to deal with dynamic webpages. It's not lightweight as jsoup as it internally using the real browser engines (headless), but there is no such limitations like in regular parser libraries with dynamic js content.

So I'm using the playwright library for a project (https://playwright.dev/java/), and I have like 4 different methods that navigate to the same page. Problem is, whenever I try to make a separate method for navigating to that part of the page, when I return that page and try to do things with it I get this error:

I'm so lost as to what to do to resolve this. I am trying to install playwright (https://playwright.dev/java/) into my Intellij IDE and I have run into so many problems. I have already tried looking for tutorial on how to do this but can't find one that helps me. I am also not familiar with Maven. I would MUCH prefer someone voice calling with me and walking me through it while I screen share than a text step-by-step. If anybody thinks they can help me with this problem, please temporarily friend me on discord, we can call and then you can unfriend me. Thanks. My disc is Sohezee#8362

Sorry. I was in shock because every time when request like this happened we asked a question about an API and if did not get anything we just told it's not possible/sustainable and client accepted it. Never I was forced to do things like that. I never would have guessed somebody does that besides of course data scrapping or SEO bots or something like that. I can't think of other solution if you really have to do that. Btw. maybe you know but if you are scrapping JS heavy apps maybe https://playwright.dev/java/ (or for other langs) would be of greater help.

Playwright supports all 3 major evergreen browsers and has Java bindings: https://github.com/microsoft/playwright-java

Java (or Kotlin): https://github.com/microsoft/playwright-java

We start with a project that was bootstrapped with npx create-next-app. For the E2E test we use Playwright and set it up as described in the testing guide provided by Next.js.

Playwright is a powerful tool developed by Microsoft, it allows developers to write reliable end-to-end tests and perform browser automation tasks with ease. What sets Playwright apart is its ability to work seamlessly across multiple browsers (Chrome, Firefox, and WebKit), it provides a consistent and efficient way to interact with web pages, extract data, and automate repetitive tasks. Moreover, it supports various programming languages such as Node.js, Python, Java, and .NET, that’s making it a versatile choice for web scraping projects. Whether you're scraping public data for analysis, building a web crawler, or automating manual workflows, Playwright has you covered.

The consensus I could gather is either use playwright or use a workaround to solve it in the puppeteer layer. The root cause of the bug is a websocket size limitation on the CDP protocol for chromium.

With the advent of tools like Puppeteer and now Playwright, end-to-end testing has become much easier and more reliable. For anyone who's used Selenium in the past, you know what I'm talking about. Puppeteer has opened the way in terms of E2E tooling, but Playwright has taken it to the next level and made it easier to await for certain selectors or conditions to be fulfilled (via locators), thus making tests more reliable and less flaky. Also, it's a game changer that it introduced a test-runner - this made the integration between the headless browser and the actual test code much smoother.

In this tutorial, our main focus will be on Playwright web scraping. So what is Playwright? It’s a handy framework created by Microsoft. It's known for making web interactions more streamlined and works reliably with all the latest browsers like WebKit, Chromium, and Firefox. You can also run tests in headless or headed mode and emulate native mobile environments like Google Chrome for Android and Mobile Safari.

// playwright.config.ts import { defineConfig } from "@playwright/test"; /** * See https://playwright.dev/docs/test-configuration. */ export default defineConfig({ testDir: "./src/pages", reporter: "list", use: { baseURL: "http://localhost:5432/", }, timeout: process.env.CI ? 10000 : 4000, // ... more options });

Issues with Playwright

Fast and reliable end-to-end testing for modern web apps | Playwright

This means you cannot place test files outside of this directory, which was brought up as a question on Github some time ago. Initially, I thought it would be nice to add another folder in the repo called "scripts", but Playwright does not allow multiple testDir values.

4.Playwright: Playwright is a browser automation library by Microsoft. Key Features: Supports Chromium, Firefox, and WebKit. Provides cross-browser testing capabilities. Allows automating web, mobile, and desktop applications