What You Need to Know: The Difference between QA & UAT

Sarah Mayfield  |  October 3, 2016

Quality Assurance (QA) and User Acceptance Testing (UAT) are sometimes underestimated in the importance of a project. Not to mention, they can be mistakenly left until the end of the project lifecycle. But both are imperative to success. So what’s the difference between them, and when should they take place?

Let’s Talk QA

At Sundog, QA is generally seen as the day-to-day check-in on a project’s layout and user functionality.

Page Templates? Check.

When creating a website, we always do a quality check as page templates are created or prototypes are added. For instance, when we set up a new homepage, we run it through BrowserStack to make sure it looks consistent through all browsers and the responsive breakpoints are reacting properly.

Browser & Mobile? Check.

Browser and mobile device requirements are discussed and agreed upon with our clients and included in our Statement of Work to ensure we are meeting client objectives. Once a page or widget has met the desired QA requirements, it’s ready to present to the client for further approval.

Now What About UAT?

UAT is slightly different. Not only does it involve checking design and basic functionality, we use UAT as the final check before a part of the project is released to production.

Put User Stories to the Test

The most efficient way to do this is to be sure that user stories or tasks have been written to meet the business requirement with success criteria that’s ultimately testable by the client.

A good example would be: “As a dealer user, I need to be able to log in and be automatically directed to the CRM home page”; this gives a clear pass/fail option to the internal and client-side testers. If the tester is able to log in as a dealer, and upon logging in is brought to the CRM home page, this test passes.

The Benefits of Weekly QA & UAT

Of course, there is still a chance of finding bugs or errors even after testing. But when you include QA and UAT as part of weekly iterations throughout the project, it’s proven to resolve issues early – and often.

And bottom line: you’ll have a higher success rate with every project.

Want to chat more about the best ways to use QA and UAT? Just send us a note. We’re here to help!

Posted in: Business Requirements, QA, Quality Assurance, UAT, User Acceptance Testing