Selenium WebDriver VS Poltergeist

Selenium is an extensively used open-source automation framework for web applications. It allows for cross-browser testing by automating browser actions, making it a staple tool for end-to-end testing in diverse web development environments.

While similar to Puppeteer, Cypress, and Selenium, there are some differences. Let’s find out what they are.

browser.get('http://selenium.dev/')

Cypress is a next-generation front-end Automation testing tool built for modern web applications. It is a JavaScript-based end-to-end testing framework and is known for faster test execution as compared with other testing tools (like Selenium or Protractor).

Removing ExpectedConditions from documentation makes sense since it was removed from the codebase around 2019 already.

https://github.com/SeleniumHQ/selenium --> trunk

You won't be able to test the javascript function itself from within python, but you can exercise the front-end code using something like cypress (https://cypress.io) or the older but still respectable selenium (https://selenium.dev).

once you solve this you may run into: https://github.com/SeleniumHQ/selenium/issues/11750, so add that workaround.

Other libraries with similar functionality are Selenium, which is very popular outside the JavaScript world, and Playwright, a younger step-brother of Puppeteer.

🔗 https://selenium.dev

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.

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.