When people hear the term quality assurance, they often think about bug testing. While finding bugs is certainly part of the process, it only scratches the surface of what quality assurance actually involves.
Much of the insight in this article comes from one of our QA Specialists, JT Wellspring, who shared his perspective on quality assurance, collaboration, real-world testing, and the role QA plays throughout our software development process.
According to JT, quality assurance is often misunderstood. While many people associate QA with bug testing alone, the work touches nearly every stage of a software project and helps ensure the final product is ready for the people who will ultimately use it. “QA ensures the final product or new feature is free of issues before being pushed to production, where real users use the system,” JT explains. “QA confirms the developers’ work and ensures there are no issues such as non-functioning buttons, pages that fail to load, or edge cases where a series of user actions causes errors.”
Those responsibilities are an important part of quality assurance, but they don’t tell the whole story. Throughout a project, QA helps validate requirements, review user experiences, confirm designs have been implemented correctly, and identify opportunities to improve how people interact with software before it reaches production.
One of the biggest misconceptions about quality assurance is that the role begins and ends with finding defects. “While it’s true that QA often just finds bugs, that isn’t the entire picture,” JT says. As software moves through development, quality assurance specialists frequently work alongside designers and developers to ensure the finished product aligns with the original intention. During testing, they may discover situations where a design was interpreted differently during development, where a workflow technically functions but creates confusion for users, or where an edge case produces an unexpected result.
Quality assurance also extends beyond a single browser or device. Applications need to function consistently across different screen sizes, operating systems, and browsers while maintaining a positive user experience. For JT, that often means evaluating software from several different perspectives at once. His work includes reviewing cross-browser functionality, testing mobile responsiveness, exploring edge cases, and ensuring applications perform as expected under a variety of conditions.
The goal is to understand not only how software is intended to be used, but also how people are likely to use it once it reaches the real world.
Many organizations think of quality assurance as a final step before launch. We weave QA throughout the development process. “From the start of the project, I attend sprint meetings,” JT says. “As the project progresses and deliverables are completed, I begin testing.”
By involving QA early, our team gains a deeper understanding of project goals, business requirements, and user expectations before features are built. That context helps uncover potential concerns sooner and creates more opportunities for feedback throughout development. “Always keeping collaboration in mind, we try to accomplish the same goal: ensuring the client’s project is the best it can be,” JT explains.
That mindset carries through the entire project. QA specialists work with developers to investigate issues and verify fixes. They work with designers to ensure the final experience reflects the original intent. They support user acceptance testing and help clients review new functionality before launch.
Rather than reviewing software only after it has been built, QA remains involved throughout the project’s evolution. That ongoing involvement helps ensure requirements, design intent, and functionality stay aligned from planning through launch.
Our work with Gleaners Food Bank of Indiana and the Groceries2Go platform provided a powerful example of why real-world testing matters. While testing in a development environment is important, there is no substitute for observing software in the environment where it will actually be used. Members of our team participated in live distribution events, watching volunteers and staff interact with the platform during active drive-thru operations.
According to JT, one of the biggest benefits of those onsite events was the opportunity to compare how people actually used the technology versus how the team initially envisioned they would use it. Those observations led to meaningful improvements. The team gained a better understanding of how volunteers with varying levels of technical experience navigated the platform and identified opportunities to simplify workflows for staff members who needed to make adjustments quickly during distributions.
The events also uncovered technical issues that would have been difficult to replicate elsewhere. “During the Gleaners drive-thru, we found that actions taken by one user affected others,” JT recalls.
“Users saw actions on their screen that they hadn’t performed.” At first glance, the issue appeared relatively small. In practice, it had the potential to create significant confusion in a high-volume environment where speed and accuracy mattered. Identifying and resolving the issue before broader rollout helped strengthen the platform and improve the experience for everyone involved.
The team also discovered smaller usability issues and opportunities to streamline processes by observing users in real time. Those findings reinforced an important lesson: software often reveals its most valuable feedback when it is placed in the hands of the people who will actually use it.
Many of the issues uncovered during quality assurance are problems users never realized existed, and that’s often the point. JT shared an example from another project involving a specialized workforce platform for the telecommunications industry. The application helped connect contractors with job opportunities and offered subscription-based account options. During a final round of testing, JT uncovered a billing issue that would have charged customers the wrong amount when switching between subscription plans. While resolving the issue delayed the production release, it prevented customer frustration, support requests, and costly refunds after launch.
Situations like these highlight the value of thorough testing. The time invested during development often prevents much larger challenges after the software reaches production. As JT puts it, “While extra testing sometimes slows the project, it actually speeds it up by reducing user issues and complexity.”
Quality assurance is ultimately about confidence. Confidence that software works as intended, that users can accomplish what they need to accomplish, and that the product is ready for the people who depend on it. By involving QA from the earliest planning discussions through launch, we create more opportunities to ask questions, validate assumptions, and improve the final product along the way. Much of the work happens behind the scenes, but its impact can be felt in every successful release.
Posted in Innovation
