UX and QA

QA is a bit like UX in a sense that although we have some professionals and roles in the development process that are meant to be solely focused on it, when in fact it has to be a concern of everyone that is involved in the process.

This is not really what happens most of the time, typically we will see a QA analyst entering the process after a development iteration, going through a list of all the developed features that have been finished and then writing descriptions about the steps and conclusions of the failed tests. In the most advanced teams and processes we get to see unit tests around the most important parts of the logic of the system, or automated end to end testing scripts that mimic the users behaviour.

It’s the goal of these procedures to catch the errors before the actual end users, this preventive model impacts in many ways the UX of the end user because not only will the system be released will less bugs and consequently less frustration for the user, but it will also have secondary effects of optimizations and different inputs when there’s a human analyst just clicking around or trying to break the flow, basically acting as a user with multiple personality disorder.

Trying to break the system is the fundamental purpose of QA, because if you break under controlled circumstances you can handle the issues that led to the actual break. But we could easily say in a different way, more focused on UX: trying to catch all frustrations the users may experience while using a system is the fundamental purpose of QA. It will still be a very on point definition of QA and it makes it clear how much UX is dependent on good QA, although the idea here is not to rewrite the definition of QA, just expose it’s close relationship with UX.

So it’s safe to say that QA is a complementary part of UX in many perspectives, it is the expression of the intention in the development process to strive for the best possible user experience, letting go of the pride or arrogance of the mentality that we get it right and simply assume we get it wrong, so let’s just improve the process so that the user doesn’t get affected by it.

This is the last post of the series, the first post in the series:

Previous post in the series:

This is part of a series of posts listed here:

--

--

--

My interests are all about engineering, entreneurship, people management, company management, product development, and overall human interaction

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

From some designer to The One Designer : The Beginning

Working With an Architect

Changes for Us, Website Tips for You

Optimize the page render of a large-scale Drupal site with several images

My DIY Book Cover Was Awful — Here’s How I Fixed It For $0

Jake Knapp’s SPRINT is Design Thinking and Lean Startup on Steroids

Week 9 — Editing Takes a Really Long Time

Blind person and person with laptop on a bench

17 Essential Tools for Graphic Designers

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Diogo Cunha

Diogo Cunha

My interests are all about engineering, entreneurship, people management, company management, product development, and overall human interaction

More from Medium

New career? Avoid these job application mistakes

NO Quality Assurance, NO ACCEPTANCE!

My Story: Become a QA at one of the biggest banks in Indonesia at the age of 19

UX process, part 2 of 4: Mapping, Testing & Envisioning