Find out how much time and equipment QA takes, and if you have the objectivity and time to handle it on your own.

1. QA Testing Primer

2. I run InteractiveQA. We provide QA Testing,
dev & strategy services. I’ve been QA’ing
websites since the mid 90s (1990s - not that
old).
http://interactiveqa.com/qa
josh@interactiveqa.com 917.620.4902
Author Bio - Josh McCormack

3. Quality Assurance testing, aka User
Acceptance testing, is simulating user
behavior to find bugs. They’re
documented, logged, assigned and
rechecked when squashed.
What is QA Testing

4. ● No automation
● No virtualization, if possible
● Tons of platforms & browsers
● Thorough banging against every link,
form and point of interaction
How do we QA?

5. About 15 minutes per page per browser. If
you’re testing against IE, FF, Chrome on
Windows, FF, Safari & Chrome on Mac,
iPhone 4 & 5, iPad & Android that’s 2.25
hours per page.
How long does it take?

6. Without multiple versions of IE or Windows
2.25 hours a page would mean 22.5 hours
for a 10 page site.

7. Oh yes.
Is QA necessary?

8. You don’t want to make clients or users
think your site isn’t worth their time.
QA is necessary

9. Probably not.
Can we do it ourselves?

10. ● Without a QA person you lack objectivity
● Do you have all the OS/browser combos
needed?
● Do you have time? We work nights and
weekends, expecting tight deadlines.

11. Developers and Project Managers should
not QA their own work. They’re too
familiar, and it’s a different expertise.
Developers & Project Managers

12. ● Errors
● Bad links
● Strange language, bad spelling
● Graphic problems
● Difficult to use
What do we check for?

13. When we test we’re trying to use your site.
It’s important people know the language
and culture super well. Our testers are
often your target audience.
Testers like Audience

14. We look forward to hearing from you.
http://interactiveqa.com/qa
josh@interactiveqa.com/qa
917.620.4902
Get in touch