Retrying e2e test suites with Jest
At Wealthfront, we pride ourselves on reliable test coverage across our codebases. However, like many engineering teams, we haven’t been able to completely eliminate flakiness from our end to end (e2e) test suites. While migrating to puppeteer certainly helped, it didn’t eliminate the problem entirely. We’ll get into what causes these flakes below, but suffice… Read more
Automating Data Quality Checks on External Data
The code was simple: query the third party API, if the “ModifiedAt” date returned was more recent than ours, send a notification to our clients. We had all the unit tests, integration tests, and monitoring in place. It had been running smoothly in production for months. So how did we end up unnecessarily sending a… Read more
One-click Developer Login
On the Wealthfront iOS team, developer productivity is a top priority. Our infrastructure engineers develop new components and APIs to enable our product engineers to ship features faster, while our product engineers are empowered to identify and eliminate toil independently. Recently, we targeted one source of toil in the development workflow by automating login within… Read more
Migrating from Capybara to Puppeteer
A little over 9 months ago, Wealthfront converted 100% of our end-to-end tests from Selenium (via Capybara) to Puppeteer. The process involved converting hundreds of tests that provide coverage for just about all of Wealthfront’s product offerings on the website. This blog post will cover why we migrated away from Selenium, the process we used… Read more
Refactoring Production Code
If you work in the software field, chances are you’ve looked at someone’s code and said to yourself, “what the hell were they thinking?!” If you’ve worked in the software field long enough, you’ve probably said the same thing about your own code: Software production and tooling has come a long way in the past… Read more
Targeting Android SDK 30
When Google announced that Play Store apps must target SDK 30 by August, our team started investigating what it would take to meet this requirement. Now, with our migration to SDK 30 complete, we’d like to detail the changes our team made. This is not meant to be an exhaustive migration guide – but hopefully… Read more