QA Testing Primer
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
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
● No automation
● No virtualization, if possible
● Tons of platforms & browsers
● Thorough banging against every link,
form and point of interaction
How do we QA?
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?
Without multiple versions of IE or Windows
2.25 hours a page would mean 22.5 hours
for a 10 page site.
Oh yes.
Is QA necessary?
You don’t want to make clients or users
think your site isn’t worth their time.
QA is necessary
Probably not.
Can we do it ourselves?
● 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.
Developers and Project Managers should
not QA their own work. They’re too
familiar, and it’s a different expertise.
Developers & Project Managers
● Errors
● Bad links
● Strange language, bad spelling
● Graphic problems
● Difficult to use
What do we check for?
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
We look forward to hearing from you.
http://interactiveqa.com/qa
josh@interactiveqa.com/qa
917.620.4902
Get in touch

QA Testing Primer

  • 1.
  • 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 minutesper 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 versionsof IE or Windows 2.25 hours a page would mean 22.5 hours for a 10 page site.
  • 7.
    Oh yes. Is QAnecessary?
  • 8.
    You don’t wantto make clients or users think your site isn’t worth their time. QA is necessary
  • 9.
    Probably not. Can wedo it ourselves?
  • 10.
    ● Without aQA 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 ProjectManagers should not QA their own work. They’re too familiar, and it’s a different expertise. Developers & Project Managers
  • 12.
    ● Errors ● Badlinks ● Strange language, bad spelling ● Graphic problems ● Difficult to use What do we check for?
  • 13.
    When we testwe’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 forwardto hearing from you. http://interactiveqa.com/qa josh@interactiveqa.com/qa 917.620.4902 Get in touch