So, we came to the conclusion that QA is not only about testing. If we are talking about QA engineers, then their task is not just to pierce all the buttons in a new feature and pierce them again before the release to make sure that nothing has fallen off. QA are involved in all stages of product development. Our goal is to release the best quality product in a reasonable time frame. We try to ensure quality at every stage of development. We monitor the quality of the code, interfaces, design and the final quality of the entire resulting product. QA can improve any of these processes.

Let me briefly remind you how we write code: what happened three years ago and what we have come to now. Two or three years ago we worked on the so-called trunk-based development. This did not suit us, and over time we switched to GitHub Flow. I already talked about how we improved this whole process and how the transition was made in a previous article, so now I will not dwell on it. Let's move on to how the whole feature development process works in general.