Quality Assurance is considered a necessary evil by some, or the guardian of an organization’s best possible self by others. But the best practices for building a good QA process are hard to pin down, and many teams struggle to build a QA practice that meets their needs. So what is good QA, and how can every team implement it?
Many teams take a “something is better than nothing” approach to QA. But what does a truly good, effective and scalable QA process look like? Let’s look at what goes into the ideal QA process, and what implementing that process looks like for a few different types of teams.
In this section, you’ll learn:
- Characteristics of Good QA
- The ideal QA workflow
- A deep dive into what makes for a good QA workflow
- What you can do to improve your QA workflow
Who owns quality and QA?
As QA teams become leaner and more focused, and testing processes become more deeply integrated with product and development workflows, knowing where the quality buck stops can be a challenge. But even for teams without a full-time QA team, having a clear, accountable quality owner is essential.
- Should Developers Own Quality? The Pros and Cons of Developer Testing Developers are taking on more and more of the QA process, especially as test automation becomes more prominent. But is handing QA over to dev teams an efficient quality hack, or a distracting time sync? Engineers Edward Paulet of Rainforest and Rob Miller from Guru discuss the pros and cons of dev-driven testing in this session.
- QA Without a QA Team Avoiding hiring a QA team entirely is an option that some Agile and CI/CD-focused organizations are testing out. During this session, Rainforest CIO Derek Choy is joined by two members of his team to discuss what QA looks like for the development and product teams here at Rainforest, in the absence of a traditional QA team.
What is a culture of quality?
Product quality is more than the sum of the tests you execute before a feature launch. Quality impacts every member of the organization, from the sales and marketing teams to developers and designers. In order to build the best possible product, teams must strive for a culture of quality, where everyone from the CEO to the interns understand quality goals and contribute to the QA process.
- How to Build a Culture of Quality: A Case Study of Twyla: The feature development process can feel mysterious and intimidating from the outside. By inviting teammates from across the organization to participate in QA activities, a product team was able to build a greater sense of confidence and product awareness at Twyla.
- Who Should Be Part of Your QA Team? Getting Creative to Build a Culture of Quality: Like all teams, QA teams can be constrained by budget considerations, or the desire to keep the team lean. By getting creative with their strategy for quality assurance, teams can tap into their broader organization to build a culture of quality that benefits everyone.
Level Up Your QA Process
Want to empower your team to deliver better quality results? Sign up for updates on exclusive QA University content. We’ll only email you when new content launches.