puppeteer
Cypress.io
Selenium
Playwright
Scrapy
Robot framework
Apify
BrowserCat
locust
Apache JMeter
Loader.io
gatling.io
k6 Cloud
Simple Analytics
LinkTiger
Google Marketing Platform
puppeteerBased on our record, puppeteer should be more popular than locust. It has been mentiond 104 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
This project tests how the browser language can be changed with Puppeteer. It implements multiple options to set the language of Chrome and checks each option against BrowserLeaks to see how it affected the JavaScript proeprties and HTTP headers available by the browser. For more information, see my article The Puppeteer Language Experiment on DEV.to. - Source: dev.to / 16 days ago
In Crawlee, you can scrape JavaScript rendered websites using the built-in headless Puppeteer and Playwright browsers. It is important to note that, by default, Crawlee scrapes in headless mode. If you don't want headless, then just set headless: false. - Source: dev.to / 17 days ago
I am not in any way associated with the developers at puppeteer, but if you are looking for a way to contribute, they are open source. - Source: dev.to / about 1 month ago
Puppeteer is a Node library that provides a high-level API to control headless Chrome or Chromium. It's primarily used for browser automation, making it a powerful tool for end-to-end testing of web applications, taking screenshots, and generating pre-rendered content from web pages. - Source: dev.to / 3 months ago
While similar to Puppeteer, Cypress, and Selenium, there are some differences. Let’s find out what they are. - Source: dev.to / 8 months ago
This week at work I was tasked with continuing some load testing that a previous Engineer had started. They had used locust which is an open source load testing tool to run the initial load testing on the staging environment. I now needed to do the same for production so I followed in their footsteps. - Source: dev.to / 2 days ago
Finally, let's compare the response time of the requests. For that, we will use Locust , an open source load testing tool. The tests will run for 5 minutes, and will increase 4 requests per second every second until they reach 1000 requests per second. - Source: dev.to / 3 months ago
Locust: Another open-source tool, Locust is particularly flexible due to its support for Python scripts. It can conduct load tests across multiple machines, making it possible to simulate millions of users simultaneously. An exceptional feature of Locust is its web-based UI, which allows real-time tracking of performance metrics during test execution. - Source: dev.to / 3 months ago
Locust is a perfect tool to use on such occasion:. - Source: dev.to / 3 months ago
So, in theory, we can handle 300 requests per minute on a single server which was the assumption we started with. After this, I decided to play with this configuration and see what we could achieve. But, to go ahead I need a system to measure the metrics of our load testing. So I quickly set up Locust on my system. Locust is an open-source easy to setup load-testing framework. - Source: dev.to / 3 months ago
Cypress.io - Slow, difficult and unreliable testing for anything that runs in a browser. Install Cypress in seconds and take the pain out of front-end testing.
Apache JMeter - Apache JMeter™.
Selenium - Selenium automates browsers. That's it! What you do with that power is entirely up to you. Primarily, it is for automating web applications for testing purposes, but is certainly not limited to just that.
Loader.io - Loader.io is a simple cloud-based load testing service
Playwright - Playwright is automation software for Chromium, Firefox, Webkit using the Node.js library having a single API in place.
gatling.io - Gatling is an open-source load testing framework based on Scala, Akka and Netty