Evergreen VS Playwright

Immy actually installs and keeps a lot of the more popular items from Ninite/Chocolatey up to date since the release of the 'Dynamic Version' feature where Immy reaches out to the vendor to get the latest version. This was inspired by https://github.com/aaronparker/evergreen and https://github.com/DanGough/Nevergreen

Evergreen (and its cousin Nevergreen) if you just want the latest installer and you want to do the rest yourself

Draw inspiration from Evergreen.

Finally, whatever you’ve uploaded to Intune will be stale as soon as an update happens to that package. Immy reaches out to the API to get the agent version that matches your instance of Automate, Control, N-Central, Ninja, Sophos, BitDefender, Printix, CloudRadial, HelpDesk Buttons, and many more. It does this also for many common line of business applications like Adobe, Bluebeam, Quickbooks, Zoom, Greenshot, 7zip, Snagit, Camtasia, I mean we add new ones daily I’m just rattling off the ones I can think of before my wife tells me to put my phone down. To be fair I have to give credit to the guys at Evergreen and Nevergreen for my inspiration. They are really doing the Lord’s work.

Example https://github.com/aaronparker/evergreen

aaronparker/Evergreen: Create evergeen Windows image build scripts with the latest version and download links for applications (github.com)

Lately I’ve been using this module, to download the binaries for the most common apps: https://github.com/aaronparker/Evergreen

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