TapReportParser
Poltergeist
Our great sponsors
| TapReportParser | Poltergeist | |
|---|---|---|
| - | 2 | |
| 3 | 2,546 | |
| - | - | |
| 0.0 | 0.0 | |
| almost 6 years ago | about 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.
TapReportParser
We haven't tracked posts mentioning TapReportParser yet.
Tracking mentions began in Dec 2020.
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?
factory_bot - A library for setting up Ruby objects as test data.
Selenium WebDriver - A browser automation framework and ecosystem.
faker - A library for generating fake data such as names, addresses, and phone numbers.
Watir - Watir Powered By Selenium
capybara-webkit
Parallel Tests - Ruby: 2 CPUs = 2x Testing Speed for RSpec, Test::Unit and Cucumber
Fix - Specing framework.
timecop - A gem providing "time travel", "time freezing", and "time acceleration" capabilities, making it simple to test time-dependent code. It provides a unified method to mock Time.now, Date.today, and DateTime.now in a single call.
API Taster - A quick and easy way to visually test your Rails application's API.
Machinist - Fixtures aren't fun. Machinist is.
cuprite - Headless Chrome/Chromium driver for Capybara