Our quick guide to pain-free testing and QA

We know the feeling. It’s finally demo day, but when you look closely your product feels incomplete and you wonder if you’ll ever meet your milestones.

The truth is quality control and testing is an important step in any product design cycle, but it can be an overwhelming moment for clients. So it’s important to know what to expect and understand how to inspect, test and give feedback to get you to the launch- ready product you dreamed of fast! All without jeopardising your deadline or compromising on quality.

‘Quality is not an act. It is a habit.’ Aristotle.

At Story of Ams we know that seamless testing aids success and helps safeguard against struggle. But, we can’t do it alone since our clients opinions are the ones that matter most. As we near the end of a project (or at critical review periods during sprints), collaboration is more important than ever in order to polish and refine your product until it’s perfect.

That is why we’ve written this handy guide to testing and quality assurance to ensure reviewing your product comes with more pleasure and less pain. Testing should be a healthy habit, not project hell.

Here are our top tips for testing;

Know what to test

Collaborate with your project team to know what is ready to test, so you don’t end up offering feedback on items still identified as ‘to-do.’

Use an objective eye

Test from two perspectives. 1. The expert that you are on your business. 2. Your users!

Understand what to look for

Does it function? and Does it flow? are your primary concerns.

Check the site structure, any features and functions and anything that can be clicked! Be aware of anything unusual, in the wrong place or disfunctional. Walk through any complex customer journeys from end to end, step by step, so you’re confident they’re complete and working well.

Once content has been added, ensure it’s flawless! That means no typos, no orphans (forgotten single words, sitting on a lonely line) and no double or missing spacing.

Give clear feedback

When you do spot something less than 100%, record it in a consistent way. Include page/page section, browser, screen size, short description, screenshots and details of what needs to change, if relevant, to ensure a speedy fix.

Agree how to supply this to your project team, as excel may not be as effective as you think!

Prioritise tasks

Work with your project team to identify those big show-stopping issues that need to be rectified before launch and the nice-to-have improvements that could be tackled later. This is especially helpful if time is short.

Manage your stakeholders

Rarely is one person responsible for reviewing and signing off a new product, but if multiple people feedback to the project team it can become counter productive. Instead, allocate a single person that can gather and consolidate feedback before offering it to the project team to minimise information overload.

Don’t go MIA at a critical moment

Collaborate with your project team to agree when you’ll respond with feedback, so they can be ready and waiting to implement changes without delay.

Have a clear definition of done

Make sure all team members are united in their definition of done, by agreeing exactly what it means for your project.

...and if you missed something major?

Tell us. ASAP. Together we’ll find a solution.

Finally, be thorough. Test not once, not twice, but multiple times to give yourself the opportunity to spot errors and issues. Why? because they’re so much easier to address at the designated time than later down the line.