Alternatives to Puppeteer logo

Alternatives to Puppeteer

Chef, Selenium, Salt, Puppet Labs, and Ansible are the most popular alternatives and competitors to Puppeteer.
290
422
+ 1
21

What is Puppeteer and what are its top alternatives?

Puppeteer is a Node library which provides a high-level API to control headless Chrome over the DevTools Protocol. It can also be configured to use full (non-headless) Chrome.
Puppeteer is a tool in the Headless Browsers category of a tech stack.
Puppeteer is an open source tool with 71.1K GitHub stars and 7.5K GitHub forks. Here’s a link to Puppeteer's open source repository on GitHub

Top Alternatives to Puppeteer

  • Chef

    Chef

    Chef enables you to manage and scale cloud infrastructure with no downtime or interruptions. Freely move applications and configurations from one cloud to another. Chef is integrated with all major cloud providers including Amazon EC2, VMWare, IBM Smartcloud, Rackspace, OpenStack, Windows Azure, HP Cloud, Google Compute Engine, Joyent Cloud and others. ...

  • Selenium

    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. Boring web-based administration tasks can (and should!) also be automated as well. ...

  • Salt

    Salt

    Salt is a new approach to infrastructure management. Easy enough to get running in minutes, scalable enough to manage tens of thousands of servers, and fast enough to communicate with them in seconds. Salt delivers a dynamic communication bus for infrastructures that can be used for orchestration, remote execution, configuration management and much more. ...

  • Puppet Labs

    Puppet Labs

    Puppet is an automated administrative engine for your Linux, Unix, and Windows systems and performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification. ...

  • Ansible

    Ansible

    Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use. ...

  • Cypress

    Cypress

    Cypress is a front end automated testing application created for the modern web. Cypress is built on a new architecture and runs in the same run-loop as the application being tested. As a result Cypress provides better, faster, and more reliable testing for anything that runs in a browser. Cypress works on any front-end framework or website. ...

  • Terraform

    Terraform

    With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel. ...

  • Playwright

    Playwright

    It is a Node library to automate the Chromium, WebKit and Firefox browsers with a single API. It enables cross-browser web automation that is ever-green, capable, reliable and fast. ...

Puppeteer alternatives & related posts

Chef logo

Chef

1.1K
929
344
Build, destroy and rebuild servers on any public or private cloud
1.1K
929
+ 1
344
PROS OF CHEF
  • 109
    Dynamic and idempotent server configuration
  • 76
    Reusable components
  • 47
    Integration testing with Vagrant
  • 43
    Repeatable
  • 30
    Mock testing with Chefspec
  • 14
    Ruby
  • 8
    Can package cookbooks to guarantee repeatability
  • 7
    Works with AWS
  • 3
    Has marketplace where you get readymade cookbooks
  • 3
    Matured product with good community support
  • 2
    Less declarative more procedural
  • 2
    Open source configuration mgmt made easy(ish)
CONS OF CHEF
    Be the first to leave a con

    related Chef posts

    In late 2013, the Operations Engineering team at PagerDuty was made up of 4 engineers, and was comprised of generalists, each of whom had one or two areas of depth. Although the Operations Team ran its own on-call, each engineering team at PagerDuty also participated on the pager.

    The Operations Engineering Team owned 150+ servers spanning multiple cloud providers, and used Chef to automate their infrastructure across the various cloud providers with a mix of completely custom cookbooks and customized community cookbooks.

    Custom cookbooks were managed by Berkshelf, andach custom cookbook contained its own tests based on ChefSpec 3, coupled with Rspec.

    Jenkins was used to GitHub for new changes and to handle unit testing of those features.

    See more
    Marcel Kornegoor

    Since #ATComputing is a vendor independent Linux and open source specialist, we do not have a favorite Linux distribution. We mainly use Ubuntu , Centos Debian , Red Hat Enterprise Linux and Fedora during our daily work. These are also the distributions we see most often used in our customers environments.

    For our #ci/cd training, we use an open source pipeline that is build around Visual Studio Code , Jenkins , VirtualBox , GitHub , Docker Kubernetes and Google Compute Engine.

    For #ServerConfigurationAndAutomation, we have embraced and contributed to Ansible mainly because it is not only flexible and powerful, but also straightforward and easier to learn than some other (open source) solutions. On the other hand: we are not affraid of Puppet Labs and Chef either.

    Currently, our most popular #programming #Language course is Python . The reason Python is so popular has to do with it's versatility, but also with its low complexity. This helps sysadmins to write scripts or simple programs to make their job less repetitive and automating things more fun. Python is also widely used to communicate with (REST) API's and for data analysis.

    See more
    Selenium logo

    Selenium

    9.8K
    7.4K
    513
    Web Browser Automation
    9.8K
    7.4K
    + 1
    513
    PROS OF SELENIUM
    • 167
      Automates browsers
    • 152
      Testing
    • 100
      Essential tool for running test automation
    • 24
      Record-Playback
    • 24
      Remote Control
    • 8
      Data crawling
    • 7
      Supports end to end testing
    • 6
      Functional testing
    • 6
      Easy set up
    • 3
      Easy to integrate with build tools
    • 3
      The Most flexible monitoring system
    • 3
      End to End Testing
    • 2
      Integration Tests
    • 2
      Comparing the performance selenium is faster than jasm
    • 2
      Record and playback
    • 2
      Compatible with Python
    • 2
      Easy to scale
    • 0
      Integrated into Selenium-Jupiter framework
    CONS OF SELENIUM
    • 5
      Flaky tests
    • 1
      Slow as needs to make browser (even with no gui)

    related Selenium posts

    Kamil Kowalski
    Lead Architect at Fresha · | 27 upvotes · 933.9K views

    When you think about test automation, it’s crucial to make it everyone’s responsibility (not just QA Engineers'). We started with Selenium and Java, but with our platform revolving around Ruby, Elixir and JavaScript, QA Engineers were left alone to automate tests. Cypress was the answer, as we could switch to JS and simply involve more people from day one. There's a downside too, as it meant testing on Chrome only, but that was "good enough" for us + if really needed we can always cover some specific cases in a different way.

    See more
    Benjamin Poon
    QA Manager - Engineering at HBC Digital · | 8 upvotes · 668K views

    For our digital QA organization to support a complex hybrid monolith/microservice architecture, our team took on the lofty goal of building out a commonized UI test automation framework. One of the primary requisites included a technical minimalist threshold such that an engineer or analyst with fundamental knowledge of JavaScript could automate their tests with greater ease. Just to list a few: - Nightwatchjs - Selenium - Cucumber - GitHub - Go.CD - Docker - ExpressJS - React - PostgreSQL

    With this structure, we're able to combine the automation efforts of each team member into a centralized repository while also providing new relevant metrics to business owners.

    See more
    Salt logo

    Salt

    380
    365
    163
    Fast, scalable and flexible software for data center automation
    380
    365
    + 1
    163
    PROS OF SALT
    • 47
      Flexible
    • 29
      Easy
    • 27
      Remote execution
    • 24
      Enormously flexible
    • 12
      Great plugin API
    • 9
      Python
    • 5
      Extensible
    • 3
      Scalable
    • 2
      nginx
    • 1
      Parallel Execution
    • 1
      Vagrant provisioner
    • 1
      Automatisation
    • 1
      HipChat
    • 1
      Best IaaC
    CONS OF SALT
    • 1
      Bloated
    • 1
      Dangerous
    • 1
      No immutable infrastructure

    related Salt posts

    Shared insights
    on
    Salt
    Puppet Labs
    Ansible
    at

    By 2014, the DevOps team at Lyft decided to port their infrastructure code from Puppet to Salt. At that point, the Puppet code based included around "10,000 lines of spaghetti-code,” which was unfamiliar and challenging to the relatively new members of the DevOps team.

    “The DevOps team felt that the Puppet infrastructure was too difficult to pick up quickly and would be impossible to introduce to [their] developers as the tool they’d use to manage their own services.”

    To determine a path forward, the team assessed both Ansible and Salt, exploring four key areas: simplicity/ease of use, maturity, performance, and community.

    They found that “Salt’s execution and state module support is more mature than Ansible’s, overall,” and that “Salt was faster than Ansible for state/playbook runs.” And while both have high levels of community support, Salt exceeded expectations in terms of friendless and responsiveness to opened issues.

    See more
    Puppet Labs logo

    Puppet Labs

    792
    659
    224
    Server automation framework and application
    792
    659
    + 1
    224
    PROS OF PUPPET LABS
    • 50
      Devops
    • 44
      Automate it
    • 26
      Reusable components
    • 21
      Dynamic and idempotent server configuration
    • 18
      Great community
    • 12
      Very scalable
    • 12
      Cloud management
    • 10
      Easy to maintain
    • 9
      Free tier
    • 6
      Works with Amazon EC2
    • 4
      Ruby
    • 4
      Declarative
    • 3
      Works with Azure
    • 3
      Works with OpenStack
    • 1
      Ease of use
    • 1
      Nginx
    CONS OF PUPPET LABS
    • 2
      Steep learning curve

    related Puppet Labs posts

    Marcel Kornegoor

    Since #ATComputing is a vendor independent Linux and open source specialist, we do not have a favorite Linux distribution. We mainly use Ubuntu , Centos Debian , Red Hat Enterprise Linux and Fedora during our daily work. These are also the distributions we see most often used in our customers environments.

    For our #ci/cd training, we use an open source pipeline that is build around Visual Studio Code , Jenkins , VirtualBox , GitHub , Docker Kubernetes and Google Compute Engine.

    For #ServerConfigurationAndAutomation, we have embraced and contributed to Ansible mainly because it is not only flexible and powerful, but also straightforward and easier to learn than some other (open source) solutions. On the other hand: we are not affraid of Puppet Labs and Chef either.

    Currently, our most popular #programming #Language course is Python . The reason Python is so popular has to do with it's versatility, but also with its low complexity. This helps sysadmins to write scripts or simple programs to make their job less repetitive and automating things more fun. Python is also widely used to communicate with (REST) API's and for data analysis.

    See more
    Shared insights
    on
    Salt
    Puppet Labs
    Ansible
    at

    By 2014, the DevOps team at Lyft decided to port their infrastructure code from Puppet to Salt. At that point, the Puppet code based included around "10,000 lines of spaghetti-code,” which was unfamiliar and challenging to the relatively new members of the DevOps team.

    “The DevOps team felt that the Puppet infrastructure was too difficult to pick up quickly and would be impossible to introduce to [their] developers as the tool they’d use to manage their own services.”

    To determine a path forward, the team assessed both Ansible and Salt, exploring four key areas: simplicity/ease of use, maturity, performance, and community.

    They found that “Salt’s execution and state module support is more mature than Ansible’s, overall,” and that “Salt was faster than Ansible for state/playbook runs.” And while both have high levels of community support, Salt exceeded expectations in terms of friendless and responsiveness to opened issues.

    See more
    Ansible logo

    Ansible

    12.8K
    10.1K
    1.3K
    Radically simple configuration-management, application deployment, task-execution, and multi-node orchestration engine
    12.8K
    10.1K
    + 1
    1.3K
    PROS OF ANSIBLE
    • 275
      Agentless
    • 204
      Great configuration
    • 192
      Simple
    • 173
      Powerful
    • 150
      Easy to learn
    • 66
      Flexible
    • 54
      Doesn't get in the way of getting s--- done
    • 33
      Makes sense
    • 29
      Super efficient and flexible
    • 27
      Powerful
    • 11
      Dynamic Inventory
    • 8
      Backed by Red Hat
    • 7
      Works with AWS
    • 6
      Cloud Oriented
    • 6
      Easy to maintain
    • 4
      Because SSH
    • 4
      Multi language
    • 4
      Easy
    • 4
      Simple
    • 4
      Procedural or declarative, or both
    • 4
      Simple and powerful
    • 3
      Vagrant provisioner
    • 3
      Consistency
    • 2
      Debugging is simple
    • 2
      Well-documented
    • 2
      Merge hash to get final configuration similar to hiera
    • 2
      Fast as hell
    • 2
      Masterless
    • 1
      Work on windows, but difficult to manage
    CONS OF ANSIBLE
    • 5
      Hard to install
    • 4
      Dangerous
    • 3
      Bloated
    • 3
      Backward compatibility
    • 2
      Doesn't Run on Windows
    • 2
      No immutable infrastructure

    related Ansible posts

    Tymoteusz Paul
    Devops guy at X20X Development LTD · | 21 upvotes · 4.3M views

    Often enough I have to explain my way of going about setting up a CI/CD pipeline with multiple deployment platforms. Since I am a bit tired of yapping the same every single time, I've decided to write it up and share with the world this way, and send people to read it instead ;). I will explain it on "live-example" of how the Rome got built, basing that current methodology exists only of readme.md and wishes of good luck (as it usually is ;)).

    It always starts with an app, whatever it may be and reading the readmes available while Vagrant and VirtualBox is installing and updating. Following that is the first hurdle to go over - convert all the instruction/scripts into Ansible playbook(s), and only stopping when doing a clear vagrant up or vagrant reload we will have a fully working environment. As our Vagrant environment is now functional, it's time to break it! This is the moment to look for how things can be done better (too rigid/too lose versioning? Sloppy environment setup?) and replace them with the right way to do stuff, one that won't bite us in the backside. This is the point, and the best opportunity, to upcycle the existing way of doing dev environment to produce a proper, production-grade product.

    I should probably digress here for a moment and explain why. I firmly believe that the way you deploy production is the same way you should deploy develop, shy of few debugging-friendly setting. This way you avoid the discrepancy between how production work vs how development works, which almost always causes major pains in the back of the neck, and with use of proper tools should mean no more work for the developers. That's why we start with Vagrant as developer boxes should be as easy as vagrant up, but the meat of our product lies in Ansible which will do meat of the work and can be applied to almost anything: AWS, bare metal, docker, LXC, in open net, behind vpn - you name it.

    We must also give proper consideration to monitoring and logging hoovering at this point. My generic answer here is to grab Elasticsearch, Kibana, and Logstash. While for different use cases there may be better solutions, this one is well battle-tested, performs reasonably and is very easy to scale both vertically (within some limits) and horizontally. Logstash rules are easy to write and are well supported in maintenance through Ansible, which as I've mentioned earlier, are at the very core of things, and creating triggers/reports and alerts based on Elastic and Kibana is generally a breeze, including some quite complex aggregations.

    If we are happy with the state of the Ansible it's time to move on and put all those roles and playbooks to work. Namely, we need something to manage our CI/CD pipelines. For me, the choice is obvious: TeamCity. It's modern, robust and unlike most of the light-weight alternatives, it's transparent. What I mean by that is that it doesn't tell you how to do things, doesn't limit your ways to deploy, or test, or package for that matter. Instead, it provides a developer-friendly and rich playground for your pipelines. You can do most the same with Jenkins, but it has a quite dated look and feel to it, while also missing some key functionality that must be brought in via plugins (like quality REST API which comes built-in with TeamCity). It also comes with all the common-handy plugins like Slack or Apache Maven integration.

    The exact flow between CI and CD varies too greatly from one application to another to describe, so I will outline a few rules that guide me in it: 1. Make build steps as small as possible. This way when something breaks, we know exactly where, without needing to dig and root around. 2. All security credentials besides development environment must be sources from individual Vault instances. Keys to those containers should exist only on the CI/CD box and accessible by a few people (the less the better). This is pretty self-explanatory, as anything besides dev may contain sensitive data and, at times, be public-facing. Because of that appropriate security must be present. TeamCity shines in this department with excellent secrets-management. 3. Every part of the build chain shall consume and produce artifacts. If it creates nothing, it likely shouldn't be its own build. This way if any issue shows up with any environment or version, all developer has to do it is grab appropriate artifacts to reproduce the issue locally. 4. Deployment builds should be directly tied to specific Git branches/tags. This enables much easier tracking of what caused an issue, including automated identifying and tagging the author (nothing like automated regression testing!).

    Speaking of deployments, I generally try to keep it simple but also with a close eye on the wallet. Because of that, I am more than happy with AWS or another cloud provider, but also constantly peeking at the loads and do we get the value of what we are paying for. Often enough the pattern of use is not constantly erratic, but rather has a firm baseline which could be migrated away from the cloud and into bare metal boxes. That is another part where this approach strongly triumphs over the common Docker and CircleCI setup, where you are very much tied in to use cloud providers and getting out is expensive. Here to embrace bare-metal hosting all you need is a help of some container-based self-hosting software, my personal preference is with Proxmox and LXC. Following that all you must write are ansible scripts to manage hardware of Proxmox, similar way as you do for Amazon EC2 (ansible supports both greatly) and you are good to go. One does not exclude another, quite the opposite, as they can live in great synergy and cut your costs dramatically (the heavier your base load, the bigger the savings) while providing production-grade resiliency.

    See more
    Sebastian Gębski

    Heroku was a decent choice to start a business, but at some point our platform was too big, too complex & too heterogenic, so Heroku started to be a constraint, not a benefit. First, we've started containerizing our apps with Docker to eliminate "works in my machine" syndrome & uniformize the environment setup. The first orchestration was composed with Docker Compose , but at some point it made sense to move it to Kubernetes. Fortunately, we've made a very good technical decision when starting our work with containers - all the container configuration & provisions HAD (since the beginning) to be done in code (Infrastructure as Code) - we've used Terraform & Ansible for that (correspondingly). This general trend of containerisation was accompanied by another, parallel & equally big project: migrating environments from Heroku to AWS: using Amazon EC2 , Amazon EKS, Amazon S3 & Amazon RDS.

    See more
    Cypress logo

    Cypress

    1K
    1.2K
    88
    Better, faster, and more reliable testing for anything that runs in a browser.
    1K
    1.2K
    + 1
    88
    PROS OF CYPRESS
    • 22
      Open source
    • 16
      Great documentation
    • 15
      Fast
    • 14
      Simple usage
    • 9
      Cross Browser testing
    • 8
      Easy us with CI
    • 4
      Npm install cypress only
    CONS OF CYPRESS
    • 15
      Cypress is weak at cross-browser testing
    • 11
      Switch tabs : Cypress can'nt support
    • 9
      No iFrame support
    • 8
      No xPath support
    • 8
      No file upload support
    • 8
      No page object support
    • 8
      No multiple domain support
    • 7
      No support for multiple tab control
    • 7
      Cypress doesn't support native app
    • 7
      Re-run failed tests retries not supported yet
    • 6
      No support for multiple browser control
    • 6
      No support for Safari
    • 4
      Adobe
    • 4
      $20/user/thread for reports
    • 4
      Not freeware
    • 3
      No 'WD wire protocol' support
    • 3
      Using a non-standard automation protocol

    related Cypress posts

    Kamil Kowalski
    Lead Architect at Fresha · | 27 upvotes · 933.9K views

    When you think about test automation, it’s crucial to make it everyone’s responsibility (not just QA Engineers'). We started with Selenium and Java, but with our platform revolving around Ruby, Elixir and JavaScript, QA Engineers were left alone to automate tests. Cypress was the answer, as we could switch to JS and simply involve more people from day one. There's a downside too, as it meant testing on Chrome only, but that was "good enough" for us + if really needed we can always cover some specific cases in a different way.

    See more
    Robert Zuber

    We are in the process of adopting Next.js as our React framework and using Storybook to help build our React components in isolation. This new part of our frontend is written in TypeScript, and we use Emotion for CSS/styling. For delivering data, we use GraphQL and Apollo. Jest, Percy, and Cypress are used for testing.

    See more
    Terraform logo

    Terraform

    9.1K
    7.2K
    299
    Describe your complete infrastructure as code and build resources across providers
    9.1K
    7.2K
    + 1
    299
    PROS OF TERRAFORM
    • 103
      Infrastructure as code
    • 71
      Declarative syntax
    • 43
      Planning
    • 26
      Simple
    • 23
      Parallelism
    • 6
      Cloud agnostic
    • 5
      It's like coding your infrastructure in simple English
    • 4
      Well-documented
    • 3
      Automates infrastructure deployments
    • 3
      Platform agnostic
    • 3
      Immutable infrastructure
    • 2
      Automation
    • 2
      Portability
    • 2
      Scales to hundreds of hosts
    • 2
      Extendable
    • 1
      Lightweight
    CONS OF TERRAFORM
    • 1
      Doesn't have full support to GKE

    related Terraform posts

    Context: I wanted to create an end to end IoT data pipeline simulation in Google Cloud IoT Core and other GCP services. I never touched Terraform meaningfully until working on this project, and it's one of the best explorations in my development career. The documentation and syntax is incredibly human-readable and friendly. I'm used to building infrastructure through the google apis via Python , but I'm so glad past Sung did not make that decision. I was tempted to use Google Cloud Deployment Manager, but the templates were a bit convoluted by first impression. I'm glad past Sung did not make this decision either.

    Solution: Leveraging Google Cloud Build Google Cloud Run Google Cloud Bigtable Google BigQuery Google Cloud Storage Google Compute Engine along with some other fun tools, I can deploy over 40 GCP resources using Terraform!

    Check Out My Architecture: CLICK ME

    Check out the GitHub repo attached

    See more
    Praveen Mooli
    Engineering Manager at Taylor and Francis · | 14 upvotes · 1.8M views

    We are in the process of building a modern content platform to deliver our content through various channels. We decided to go with Microservices architecture as we wanted scale. Microservice architecture style is an approach to developing an application as a suite of small independently deployable services built around specific business capabilities. You can gain modularity, extensive parallelism and cost-effective scaling by deploying services across many distributed servers. Microservices modularity facilitates independent updates/deployments, and helps to avoid single point of failure, which can help prevent large-scale outages. We also decided to use Event Driven Architecture pattern which is a popular distributed asynchronous architecture pattern used to produce highly scalable applications. The event-driven architecture is made up of highly decoupled, single-purpose event processing components that asynchronously receive and process events.

    To build our #Backend capabilities we decided to use the following: 1. #Microservices - Java with Spring Boot , Node.js with ExpressJS and Python with Flask 2. #Eventsourcingframework - Amazon Kinesis , Amazon Kinesis Firehose , Amazon SNS , Amazon SQS, AWS Lambda 3. #Data - Amazon RDS , Amazon DynamoDB , Amazon S3 , MongoDB Atlas

    To build #Webapps we decided to use Angular 2 with RxJS

    #Devops - GitHub , Travis CI , Terraform , Docker , Serverless

    See more
    Playwright logo

    Playwright

    53
    141
    26
    Node library to automate Chromium, Firefox and WebKit with a single API (By Microsoft)
    53
    141
    + 1
    26
    PROS OF PLAYWRIGHT
    • 9
      Cross browser
    • 5
      Open source
    • 4
      Test Runner with Playwright/test
    • 4
      Well documented
    • 4
      Promise based
    CONS OF PLAYWRIGHT
    • 3
      Less help

    related Playwright posts