Everyone at Monzo gets involved in testing new features and versions of the app before we release them. @Dropkick, one of our Quality Assurance testing team members, explains the different types of testing we do and how.
Sarah has also been kind enough to answer any questions that the Community might have on the back of their blog.
We do a bit of both Test-Driven-Development and Behaviour-Driven-Development. We write our test plans based on Acceptance criteria before the implementation starts and then we host Squad Test Parties before we ship.
Depending on the feature we also write or re-write our automation tests along side shipping.
I’m amazed you only have 4 testers, that doesn’t seem like enough to me?
You talk in the article a lot about the front end i.e. the apps but I don’t really see anything about the backend. Do you get involved in performance testing and disaster recovery type scenarios or anything like that?
I worked in testing for about 10/12 years in telecoms but always on the backend systems really, hence my questions
This is an interesting point. I guess this might not get answered, but how many squads does Monzo have for development? If it’s say 5-6 and the squads are responsible for testing themselves, using the 4 testers to coach and guide then I can see how this might work.
If monzo has 4 squads (iOS, Android, web, business systems?) then again that makes sense. If however there are +6 squads in the business yet only 4 testers then
I get you can have automated tests that will run on commit, and that the branch will do the “heavy lifting” of testing so that the manual testers will be a check/fallback if something is flagged but that still seems low.
So, either Monzo hasn’t got enough testers, or it has enough but it might explain how things like trends took so long to roll out, cos they only have a few squads?