Why have we decided to not use QA teams? How to build a good strategy for automatic tests? And how can we make sure that we cover every potential bug in our code?
At monday, we don’t have a QA department. With that being said, just like every other company, it’s important to us to make sure our R&D department runs as fast as possible (and still allow our developers to sleep at night). So how do we do it?
In one of our Unplugged engineering sessions, Shanee Radzewsky, a Full-Stack developer on the Autopilot Core team at monday, shared how we built a good testing strategy incorporated into every level of the R&D. A strategy that will allow us to continue moving quickly in our R&D department, without relying on a QA team. In this week’s episode we bring the main insight from her session
Under this description is a link to the original session’s presentation, and we recommend looking at it while listening.
And a short reminder – this episode is not a technical one, and is suited to managers or founders wanting to learn more about the subject, or test their engineering department work methods.
Link to the session – https://www.youtube.com/watch?v=XWkQDPAOc9E&t=20s
Link to the presentation- https://drive.google.com/file/d/1Bx8wR0eR8YebkVLig0mfLxquaBxMjPXV/view?usp=sharing
More relevant episodes:
First R&D mini-series episode – The core principles of our R&D culture