lighthouse-ci
WebdriverIO
Our great sponsors
lighthouse-ci | WebdriverIO | |
---|---|---|
18 | 36 | |
6,223 | 8,736 | |
1.3% | 3.1% | |
7.2 | 9.9 | |
7 days ago | about 4 hours ago | |
JavaScript | TypeScript | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
lighthouse-ci
-
help needed with lighthouse ci for angular, github actions, PROTOCOL_TIMEOUT: (Method: Debugger.disable)
- 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,
-
Continuous performance audits in Nuxt with Lighthouse CI and Github Actions
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.
-
Ensure your Next.js app's performance is top-notch with Lighthouse CI and GitHub Actions
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.
-
Everything you need to know about Web Performance (in 5 Minutes)
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.
-
Understanding SEO and Web Vitals for your NextJS site and how to improve them?
You can also set up lighthouse-ci as a github action to evaluate the web vitals on push or in pull requests.
-
Frontend Testing: No more Unit/Integration/E2E categorizations and priorities
This name is already self-explanatory, and developers just need to run Lighthouse or its CI.
-
I built an open-source tool that scans your entire website with Google Lighthouse (unlighthouse.dev)
They also have a powerful CI tool (https://github.com/GoogleChrome/lighthouse-ci) with custom timelines, may look to implement it at some point
-
10 Tools to measure Core Web Vitals
Lab data on demand and unattended. This version of Lighthouse is oriented to be integrated in a continuous integration workflow to check your metrics before deploying to production. However, you could also use it as command executed in a cron to check an environment performance over the time. I use the latter to check production performance each 12 hours, since there are third parties adding and removing dynamic content that could affect UX. Check its repo here
-
Continuous performance checks in Nuxt.js with Lighthouse CI and Github Actions
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.
-
The Frontend Hitchhikers Guide: Testing
Lighthouse audits performance according to the core web vitals. Additionally, lighthouse can audit for Accessibility, Best Practices, Search Engine Optimization and whether your page is a Progressive Web App. You can also automate lighthouse audits via its API. Its a great tool to ensure your app is fast and does well with google search.
WebdriverIO
-
Way to High Confidence: The Ideal Testing Trophy
Webdriver.io
-
Battle-Testing Nx Console with E2E Tests
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.
-
Projects Coming to Life 🌈 Inside of VS Code - Marquee's Project Mode
Curate your repo’s dashboard for your team’s benefit by checking in relevant VS Code settings into your version control system. Install Marquee and give it a shot.
-
Wizard level tips for testing/QA JS browser code ? How do you ensure full coverage, generate test cases, etc ?
My team uses Vue.js. We use Karma/Mocha/Chai and Sinon and Vue Test Utils to test our Vue components. For E2E testing we use Webdriver.io, but have in the past used Selenium written in Kotlin, and also Cypress.
-
Breaking changes between 14 and 16?
There were changes to node-fibers that broke at least one thing I used, the sync mode of WebdriverIO. https://github.com/webdriverio/webdriverio/discussions/6702
-
WebdriverIO supports Chaining without multiple await statements
Ever since WebdriverIO got launched, major companies adopted this tool for automation. It became popular very fast due to its powerful advantages. Since the launch, there have been lots of changes and improvements being made to the tool. In this article, we'll be discussing one of the improvements that have really helped us in writing automation scripts in async mode.
WebdriverIO is asynchronous by nature. Earlier, WebdriverIO used to provide the ability to run commands in sync mode using node-fibers. However, due to some breaking changes in Chromium, WebdriverIO discontinued the support for sync mode. Please refer Sync vs. Async Mode and this issue for more information.
-
Advanced Roadmap for React.js developers
-Selenium -Webdriver -Cypress -Puppeteer -Cucumber.js -Nightwatch.js
-
The React roadmap for beginners you never knew you needed.
Selenium, Webdriver
-
Github Actions for Seleniod Test Scripts
In this article, we are going to see how to automate a web application using WebdriverIO. Leveraging the cross-browser power of Selenoid, by running it on the GitHub Actions and publishing the test results to GitHub pages.
What are some alternatives?
Playwright - Playwright is a framework for Web Testing and Automation. It allows testing Chromium, Firefox and WebKit with a single API.
jest - Delightful JavaScript Testing.
TestCafe - A Node.js tool to automate end-to-end web testing.
Protractor - E2E test framework for Angular apps
nightwatch - Integrated end-to-end testing framework written in Node.js and using W3C Webdriver API. Developed at @browserstack
CodeceptJS - Supercharged End 2 End Testing Framework for NodeJS
pa11y - Pa11y is your automated accessibility testing pal
Cypress - Fast, easy and reliable testing for anything that runs in a browser.
istanbul - Yet another JS code coverage tool that computes statement, line, function and branch coverage with module loader hooks to transparently add coverage when running tests. Supports all JS coverage use cases including unit tests, server side functional tests and browser tests. Built for scale.
electron-spectron-example - A example of using Spectron to test an Electron application
puppeteer - Node.js API for Chrome
karma - Spectacular Test Runner for JavaScript