Watir VS Poltergeist

Compare Watir vs Poltergeist and see what are their differences.

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
Watir Poltergeist
- 2
1,506 2,546
0.3% -
6.0 0.0
4 months ago about 5 years ago
Ruby Ruby
MIT License MIT License
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

Watir

Posts with mentions or reviews of Watir. We have used some of these posts to build our list of alternatives and similar projects.

We haven't tracked posts mentioning Watir yet.
Tracking mentions began in Dec 2020.

Poltergeist

Posts with mentions or reviews of Poltergeist. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-10-04.
  • Stripe Financial Connections
    1 project | news.ycombinator.com | 4 May 2022
    Hostile integrations using scripts to obtain financial data is trivial. Frameworks such as:

    https://github.com/teampoltergeist/poltergeist

    is an excellent example of such a framework. Implementing "bank drivers" using such frameworks would not be difficult.

    Plaid and others seem to have done an awesome job scaling the hostile integration pattern. However, the idea that Stripe decided to build this in-house rather than rely on Plaid is perfectly reasonable.

    After all, the tools to implement such a product are well known.

  • Migrating Selenium system tests to Cuprite
    10 projects | dev.to | 4 Oct 2021
    In our project, we’ve been running system tests (then called rather "Feature tests") since around 2016. System tests use a real browser in the background and test all layers of a Rails application at once: from the database all the way up to the nuances of JavaScript loaded together with the web pages. Back then, we wrote our system tests using Capybara with Poltergeist, a driver that ran a headless Phantom JS browser. Since this browser stopped being actively developed, we migrated our test suite to the Selenium / Webdriver wrapper around Chrome browser around ~2018. Chrome was itself fine for tests automation but the Selenium API was quite limited and we had to rewrite several Poltergeist features using 3rd party gems and tools.

What are some alternatives?

When comparing Watir and Poltergeist you can also consider the following projects:

Selenium WebDriver - A browser automation framework and ecosystem.

capybara-webkit

API Taster - A quick and easy way to visually test your Rails application's API.

Fix - Specing framework.

Ruby Tests Profiling Toolbox - Ruby Tests Profiling Toolbox

TapReportParser - TAP Report Parser

turbo_tests - Run RSpec tests on multiple cores. Like parallel_tests but with incremental summarized output. Originally extracted from the Discourse and Rubygems source code.

cuprite - Headless Chrome/Chromium driver for Capybara