Alternatives to Chromeless logo

Alternatives to Chromeless

PhantomJS, Selenium, Puppeteer, jsdom, and Playwright are the most popular alternatives and competitors to Chromeless.
9
27
+ 1
0

What is Chromeless and what are its top alternatives?

Chrome automation made simple. Runs locally or headless on AWS Lambda.
Chromeless is a tool in the Headless Browsers category of a tech stack.
Chromeless is an open source tool with GitHub stars and GitHub forks. Here鈥檚 a link to Chromeless's open source repository on GitHub

Top Alternatives to Chromeless

  • PhantomJS
    PhantomJS

    PhantomJS is a headless WebKit scriptable with JavaScript. It is used by hundreds of developers and dozens of organizations for web-related development workflow. ...

  • 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. ...

  • Puppeteer
    Puppeteer

    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. ...

  • 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. ...

  • jsdom
    jsdom

    It is a pure-JavaScript implementation of many web standards, notably the WHATWG DOM and HTML Standards, for use with Node.js. In general, the goal of the project is to emulate enough of a subset of a web browser to be useful for testing and scraping real-world web applications. ...

  • CasperJS
    CasperJS

    CasperJS is a browser navigation scripting & testing utility written in Javascript for PhantomJS or SlimerJS. ...

  • Splash
    Splash

    It is a headless browser that executes JavaScript for people crawling websites. It is open source and fully integrated with Scrapy and Portia. You can also use its API to integrate with any project that needs to render JavaScript pages. ...

  • Serverless Chrome
    Serverless Chrome

    The aim of this project is to provide the scaffolding for using Headless Chrome during a serverless function invocation. Serverless Chrome takes care of building and bundling the Chrome binaries and making sure Chrome is running when your serverless function executes. In addition, this project also provides a few "example" handlers for common patterns (e.g. taking a screenshot of a page, printing to PDF, some scraping, etc.) ...

Chromeless alternatives & related posts

PhantomJS logo

PhantomJS

489
425
18
Scriptable Headless WebKit
489
425
+ 1
18
PROS OF PHANTOMJS
  • 13
    Scriptable web browser
  • 3
    Depends on QT
  • 2
    No ECMAScript 6
CONS OF PHANTOMJS
    Be the first to leave a con

    related PhantomJS posts

    Tim Abbott

    We use CasperJS because we adopted it back in 2013 for JavaScript frontend testing. It was a really nice system back then compared to what else was out there; you had PhantomJS as a programmable browser that actually rendered CSS and everything, it was really fast (speed is a big downside of e.g. Selenium), and it was possible to make non-flaky frontend integration tests with it.

    I wouldn't recommend it today, because PhantomJS is a basically dead project, and as a result, so is CasperJS. I expect we'll migrate to something else. We haven't in large part because 95% of our new tests are written with a simple Node.js-based unit testing framework we use that run 35K lines of unit tests covering most of our JS codebase in 3.6 seconds. And for the things where we want an integration test, CasperJS does work, and I think there's a good chance that waiting another year or two will result in our being able to switch to a much better option than what we'd get if we migrated now.

    See more
    Selenium logo

    Selenium

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

    related Selenium posts

    Kamil Kowalski
    Lead Architect at Fresha | 28 upvotes 路 1.9M views

    When you think about test automation, it鈥檚 crucial to make it everyone鈥檚 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 路 975K 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
    Puppeteer logo

    Puppeteer

    383
    548
    26
    Headless Chrome Node API
    383
    548
    + 1
    26
    PROS OF PUPPETEER
    • 10
      Very well documented
    • 10
      Scriptable web browser
    • 6
      Promise based
    CONS OF PUPPETEER
    • 10
      Chrome only

    related Puppeteer posts

    Raziel Alron
    Automation Engineer at Tipalti | 7 upvotes 路 333.8K views

    Currently, we are using Protractor in our project. Since Protractor isn't updated anymore, we are looking for a new tool. The strongest suggestions are WebdriverIO or Puppeteer. Please help me figure out what tool would make the transition fastest and easiest. Please note that Protractor uses its own locator system, and we want the switch to be as simple as possible. Thank you!

    See more

    I work in a company building web apps with AngularJS. I started using Selenium for tests automation, as I am more familiar with Python. However, I found some difficulties, like the impossibility of using IDs and fixed lists of classes, ending up with using xpaths most, which unfortunately could change with fixes and modifications in the code.

    So, I started using Puppeteer, but I am still learning. It seems easier to find elements on the webpage, even if the creation and managing of arrays of elements seem to be a little bit more complicated than in Selenium, but it could be also due to my poor knowledge of JavaScript.

    Any comments on this comparison and also on comparisons with similar tools are welcome! :)

    See more
    Playwright logo

    Playwright

    254
    451
    75
    Node library to automate Chromium, Firefox and WebKit with a single API (By Microsoft)
    254
    451
    + 1
    75
    PROS OF PLAYWRIGHT
    • 13
      Cross browser
    • 9
      Open source
    • 9
      Test Runner with Playwright/test
    • 7
      Well documented
    • 7
      Promise based
    • 5
      Integrate your POMs as extensible fixtures
    • 5
      API Testing
    • 5
      Execute tests in parallel
    • 4
      Capture videos, screenshots and other artifacts on fail
    • 4
      Python Support
    • 3
      Context isolation
    • 3
      Inbuild reporters html,line,dot,json
    • 1
      Fastest
    CONS OF PLAYWRIGHT
    • 11
      Less help
    • 2
      Node based
    • 1
      Does not execute outside of browser

    related Playwright posts

    jsdom logo

    jsdom

    231
    49
    1
    A JavaScript implementation of the WHATWG DOM and HTML standards, for use with node.js
    231
    49
    + 1
    1
    PROS OF JSDOM
    • 1
      Lightweight
    CONS OF JSDOM
      Be the first to leave a con

      related jsdom posts

      CasperJS logo

      CasperJS

      60
      119
      0
      Navigation scripting & testing for PhantomJS and SlimerJS
      60
      119
      + 1
      0
      PROS OF CASPERJS
        Be the first to leave a pro
        CONS OF CASPERJS
          Be the first to leave a con

          related CasperJS posts

          Tim Abbott

          We use CasperJS because we adopted it back in 2013 for JavaScript frontend testing. It was a really nice system back then compared to what else was out there; you had PhantomJS as a programmable browser that actually rendered CSS and everything, it was really fast (speed is a big downside of e.g. Selenium), and it was possible to make non-flaky frontend integration tests with it.

          I wouldn't recommend it today, because PhantomJS is a basically dead project, and as a result, so is CasperJS. I expect we'll migrate to something else. We haven't in large part because 95% of our new tests are written with a simple Node.js-based unit testing framework we use that run 35K lines of unit tests covering most of our JS codebase in 3.6 seconds. And for the things where we want an integration test, CasperJS does work, and I think there's a good chance that waiting another year or two will result in our being able to switch to a much better option than what we'd get if we migrated now.

          See more
          Splash logo

          Splash

          26
          32
          0
          Headless browser that executes JavaScript for people crawling websites
          26
          32
          + 1
          0
          PROS OF SPLASH
            Be the first to leave a pro
            CONS OF SPLASH
              Be the first to leave a con

              related Splash posts

              Serverless Chrome logo

              Serverless Chrome

              8
              24
              0
              Headless Chrome on AWS Lambda
              8
              24
              + 1
              0
              PROS OF SERVERLESS CHROME
                Be the first to leave a pro
                CONS OF SERVERLESS CHROME
                  Be the first to leave a con

                  related Serverless Chrome posts