Fred Stevens-Smith, the co-founder and CEO of Rainforest QA, emphasizes that quality assurance (QA) is not just about testing functionality but about fostering a mindset within the entire product team. In his insights, drawn from over a decade of experience working with QA in various software teams, Stevens-Smith argues that product teams—including product managers (PMs), developers, and designers—must collaborate to ensure quality. He challenges the traditional view that QA teams alone are responsible for quality, asserting that product teams must own this responsibility, as they are ultimately accountable for delivering features to customers.

A key lesson Stevens-Smith highlights is that QA professionals cannot solve quality problems by themselves. The real challenge lies in building a culture of quality across the entire team. If developers and PMs lack the proper mindset and incentives around quality, then no matter how good the QA team is, high-quality products won’t be delivered. This lesson reflects Stevens-Smith's experience, including his company’s own pivot from a crowd-testing platform to no-code automation, based on the realization that their original approach didn’t improve quality enough for customers.

Stevens-Smith's first principle is that product teams, not QA, must own quality. The product manager, in particular, plays a crucial role in this. PMs are responsible for shipping features that solve customer problems, and they are held accountable if a product is released with issues. While developers are key stakeholders in ensuring quality, their focus is often limited to code quality. This narrow view doesn't always address the overall user experience. Stevens-Smith emphasizes that quality must be seen more broadly, encompassing both technical correctness and user satisfaction.

One of his key principles is that testing should be conducted in a way that reflects how a human would use the software. According to Stevens-Smith, many companies make the mistake of relying too heavily on automated testing that focuses on technical aspects, such as inspecting the DOM (Document Object Model). However, users do not interact with software this way; they simply click buttons and expect it to work. He advises testing the software as a real user would to ensure that the user experience is aligned with expectations.

Another significant point Stevens-Smith makes is about the risk of over-testing. He explains that too much testing, particularly automated testing, can be as harmful as too little testing. Many organizations fall into the trap of writing hundreds of tests, only to find that a large proportion of them fail or provide unreliable results. Instead of adding more tests, the focus should be on improving the quality of the existing tests and making it easier to uncover real issues before the product is shipped. Stevens-Smith warns that over-testing can shift attention away from the core goal of identifying and fixing user experience issues.

In summary, Fred Stevens-Smith advocates for a shift in how teams approach quality assurance. He emphasizes that QA is not solely the responsibility of a separate team but should be a shared goal across the entire product team. By focusing on creating a culture of quality, testing like a human, and avoiding excessive testing, Stevens-Smith believes teams can significantly improve the quality of the software they deliver to their customers.

https://www.linkedin.com/in/fredstevenssmith/