A Look Inside Build Testing at Wealthsimple
On Thursdays, we build test.
We previously covered how Wealthsimple ships new features with our mobile app release cycle. In this post, we’re diving into weekly build testing, which is a major part of how we #ship-it with confidence.
Why Manual End-To-End (E2E) Testing?
We build for the client. The best way to understand how the client will feel using our app is to use it ourselves.
While E2E automation excels at testing completeness of flows and business logic, it cannot yet verify user experience (ease of use, lagging, intuitive design, etc.). That’s why manual build testing is still so important.
How It Works
Every Thursday, a designated engineer from each product team runs end-to-end tests on our latest build of the mobile app, before we release it to clients.
A designated “App Release Conductor” is assigned to track and triage reported bugs, and monitor the app release rollout.
Found a Bug?
When a bug is found, we are required to fix it before our app is submitted to the app stores for release. Some examples of critical bugs are when:
- Signup and login flows are negatively affected
- Significant performance regressions are found
- Data is delayed or lagging
Hot-Fix and Release
Teams work throughout the day to add necessary fixes into a release/hotfixes git branch. Once all hot-fixes are merged, we progressively rollout a new app version.
During rollout of a new build, our App Release Conductor monitors performance metrics, crash reports, and client feedback, and coordinates a patch release when necessary.
Thanks for coming to build testing. We’ll be back next week to do it again.
_________________________________________________________________________________________________
Written by Anisha Latchman, Software Developer Intern
Interested in working at Wealthsimple? Check out open roles on our team today.