Everyone is talking about DevOps but what about DevQA? In addition to analytical and logical thinking testers must know notions of programming and also coding, same as for writing simple unit test scripts. They must know about concepts of databases, web services, build systems and continuous integration. A DevQA stimulates the testing area to expand their knowledge leading out of the comfort zone where once almost manual activities were repeated throughout the development of a system. They have an obligation to reinvent their activities and assisting the team in others, being more integrated and participatory. This is the story how we went from Quality Control to Quality Assistance. How we managed required organisational changes and setting up an automation strategy which lead the way from Quality Control to Quality Assurance. Later on we realised this is not enough as traditional testers help to ship safely by doing the testing, but this can have the side-effect of slowing the team down. Our tester:developer ratio was always low we had to find a way to empower and educate developers to test their features according to quality standards. We evolved this over time also to enforce the “whole team” mentality when it comes to quality. As developers learn to build quality into their features from the start, rework is reduced, and the team can achieve both quick and safe delivery. A DevQA becomes the facilitator for this, instead of the individual performing the tests. This transition is what we called “quality assistance”.