Now meet the full-stack QA tester

There’s a perception that QA engineers are far less technical than developers, engaged primarily with manual testing of whatever the developer happens to hand over to them. This myth paints testers as being primarily reactive, looking for bugs in work that has been finished by the developers, rather than proactively looking for defects throughout the planning, design and development stages as well.

There may have been some truth in this when we were doing most of our development in waterfall style, but in today’s agile and DevOps organization, this is an outdated and inaccurate view. In today’s organization, you’re pretty much guaranteed to work with full-stack QA engineers. Let me explain.

A developer who masters each layer of an application, and the technologies employed all the way through from the back-end to the front-end, is called a full-stack developer.  Similarly, a QA engineer working on all aspects of quality and using different testing methods to test their application, is called a full-stack QA engineer. A full-stack QA engineer will be comfortable working across all of the application’s layers, and will be familiar with large parts of its functionality. They will think about the many different aspects of product quality, such as functionality, usability, performance, security, globalization and so on.  They will be familiar with test automation strategies and technologies. The full-stack QA engineer has a rich mix of domain knowledge, technical skills and testing expertise, all from a user-oriented perspective.

Leave a Reply