How We Do Quality Assurance

Maddie Lucas

The Breakdown: Quality Assurance

Quality assurance. It can mean very different things to different companies. To us, quality assurance (QA) is simply making sure that there are no complications for our clients and their users. We want to make sure that each website we create is delivering the best possible product. This can be done by looking for technical issues and ways to improve the overall project. Matt Schnepf, our QA analyst, explains what he does on a daily basis to keep the websites that we create top-notch.

What Goes into QA?

It is usually a 3 step process to create a user-friendly and quality site.

Matt creates pages for new websites and fills them with “test content” so that the designs our clients love are being reflected when they see their finished site.
After creating pages, he starts exploring and testing the website by doing actions that might break it. This could be as simple as using an image that is too large or small, or as complex as trying to break a form with javascript entered in the fields. He evaluates any issues that might come up and works with our developers to find solutions by suggesting things that they can do to make it an easier experience for the user.

Matt writes “bug reports” that describe what the issue is, and how to recreate it. Then, it goes off to the developers who re-create and solve it. After the problem is solved, Matt retests it to verify that there are no complications from the fix and that everything is working smoothly.

The Process

QA is a small part of almost every step in our process, making it a very big part of what we do. For smaller projects, we found that it is best to use the waterfall method. In this method, after the site is developed, Matt will do the testing. For our bigger projects, we use the agile method. In this method, QA is tested during the development process. No matter how a website is tested for quality assurance, Matt works hand-in-hand with almost every department including project managementUXdesignfront-end and back-end development, and content strategy, making sure that there are no issues along the way.

Common Misconceptions

Wearing Two Hats

People may think that quality assurance is just about finding bugs or using software. “When I worked in QA for a video game developer, I was always asked if my job was being payed to play a game,” explains Matt. But it’s much more than that. Not only does Matt have to think like a developer, he also has to view software from the perspective of users.

When doing this, he can’t only think about how most people may use the site. He also views the site with a wide range of perspectives and intentions. For example, some users may have nefarious purposes when visiting a site, while other users may have simple expectations like clicking on a link once rather than twice to open it. By keeping these perspectives in mind, Matt can find solutions that work for both the client and their users.

Solving Problems

Another misconception is that QA work is simple, when in reality it can be like solving a complicated puzzle. Some issues have simple solutions with understandable causes and effects. Often, there are much more complicated bugs that don’t have an obvious cause. Matt works backwards using logic and out-of-the-box thinking to successfully reproduce the issue and solve it. Solving these unique problems can be quite challenging, but this is also what Matt finds the most satisfying.

“The most challenging part is also the part I love the most — the puzzle-like nature of complicated issues,” explains Matt.


Want to learn more about quality assurance? Check out these favorite resources from Matt:

Connect with us on social media to keep up with our team, blog posts, projects, events, and more.


Facebook: SiteCrafting
Twitter: @SiteCrafting
Instagram: @SiteCrafting
LinkedIn: SiteCrafting


Facebook: GearLab
Twitter: @GearLabNW
Instagram: @GearLabNW
LinkedIn: GearLab