puffing-billy
Poltergeist
puffing-billy | Poltergeist | |
---|---|---|
2 | 2 | |
652 | 2,546 | |
- | - | |
4.4 | 0.0 | |
7 days ago | over 5 years ago | |
Ruby | Ruby | |
MIT License | 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.
puffing-billy
-
puffing-billy VS vcr - a user suggested alternative
2 projects | 7 Oct 2021
-
Migrating Selenium system tests to Cuprite
For a lot of these features, we previously had to adopt various 3rd party gems, such as the Puffing Billy proxy (for blocking domains), the webdrivers gem (for auto-updating the Chrome drivers), etc. and although they certainly did a good job for us, now we were able to finally rip them off the project completely:
Poltergeist
-
Stripe Financial Connections
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
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?
vcr - Record your test suite's HTTP interactions and replay them during future test runs for fast, deterministic, accurate tests.
Selenium WebDriver - A browser automation framework and ecosystem.
ferrum - Headless Chrome Ruby API
Watir - Watir Powered By Selenium
cuprite - Headless Chrome/Chromium driver for Capybara
capybara-webkit
Fix - Specing framework.
webdrivers - Keep your Selenium WebDrivers updated automatically
API Taster - A quick and easy way to visually test your Rails application's API.
stimulus-use - A collection of composable behaviors for your Stimulus Controllers
TapReportParser - TAP Report Parser