lighthouse-ci VS WebdriverIO

- referred to https://github.com/GoogleChrome/lighthouse/issues/6512 but didnt see network.disable error - added staticdistdir as per https://github.com/GoogleChrome/lighthouse-ci/blob/main/docs/configuration.md,

This approach would suit most of the cases however to achieve more accurate performance audits you should be conducting Lighthouse tests on a dedicated server to avoid results being affected by the machine capabilities. In other words, if you are running Lighthouse audits on a repository where there are several pull requests/workflows/pushes going on, the result of this audit may not be accurate and this is what we want to avoid. For that you would need a separate machine with Lighthouse Server installed on it. So on a pull request you would trigger this machine to conduct a performance audit and return response to your repository.

And finally, Lighthouse has a CI version you can run in your continuous integration. We’ll use this method to schedule periodical benchmarks.

TLDR; I use the Google Chrome Lighthouse CI with a .lighthouserc json configuration to test next start. The Lighthouse CI GitHub app is used to return a pass or fail status check in a PR.

You should also incorporate performance checks into your CI/CD pipeline. Use Lighthouse CI to run a synthetic Lighthouse test on each PR (PS: Learn why you shouldn't believe the Lighthouse score alone) and bundlesize package to raise alerts if your bundle size exceeds a certain threshold. For more nuanced data you should use WebPageTest.

You can also run Google’s Lighthouse CI tool against multiple URLs, and then hook that up to their self-hosted dashboard service: https://github.com/GoogleChrome/lighthouse-ci

You can also set up lighthouse-ci as a github action to evaluate the web vitals on push or in pull requests.

You can have more consistent results if you set up Lighthouse CI in an external environment to test your page or use tools like SpeedCurve, but if you need to quickly inspect a website, I suggest taking a look at Page Speed Insights.

This name is already self-explanatory, and developers just need to run Lighthouse or its CI.

They also have a powerful CI tool (https://github.com/GoogleChrome/lighthouse-ci) with custom timelines, may look to implement it at some point

3.WebdriverIO: WebdriverIO is another popular open-source test automation framework. Key Features: Integrates well with popular testing frameworks (e.g., Mocha, Jasmine). Supports both synchronous and asynchronous commands. Works with various browsers and platforms

Webdriver.io

There is a tool called webdriver.io which purports to handle mobile automation. I haven't had a chance to play with it yet but it's on my radar.

We recently hired an engineer to write us integration tests with webdriver.io. All of our other tests run fine in Github actions - rspec, javascript jest, etc.

Your automated tests will act on behalf of a real user, open a real web browser (typically Chromium, Chrome, Firefox) using one an existing technology like Webdriver and add some syntactical sugar on top.

WebdriverIO (abbreviated as WDIO) is an E2E testing framework for Node.js. It allows you to automate all kinds of web and mobile applications using the Webdriver or Chrome DevTools protocols.

i recall having to deal with elements inside iframes and shadow roots when using webdriver.io for testing. you can always inspect an element and copy the selector. if it is unique to the page it should work