OneStopTesting - Quality Testing Jobs, eBooks, Articles, FAQs, Training Institutes, Testing Software, Testing downloads, testing news, testing tools, learn testing, manual testing, automated testing, load runner, winrunner, test director, silk test, STLC

Forum| Contact Us| Testimonials| Sitemap| Employee Referrals| News| Articles| Feedback| Enquiry
 
Testing Resources
 
  • Testing Articles
  • Testing Books
  • Testing Certification
  • Testing FAQs
  • Testing Downloads
  • Testing Interview Questions
  • Career In Software Testing
  • Testing Jobs
  • Testing Job Consultants
  • Testing News
  • Testing Training Institutes
  •  
    Fundamentals
     
  • Introduction
  • Designing Test Cases
  • Developing Test Cases
  • Writing Test Cases
  • Test Case Templates
  • Purpose
  • What Is a Good Test Case?
  • Test Specifications
  • UML
  • Scenario Testing
  • Test Script
  • Test Summary Report
  • Test Data
  • Defect Tracking
  •  
    Software testing
     
  • Testing Forum
  • Introduction
  • Testing Start Process
  • Testing Stop Process
  • Testing Strategy
  • Risk Analysis
  • Software Listings
  • Test Metrics
  • Release Life Cycle
  • Interoperability Testing
  • Extreme Programming
  • Cyclomatic Complexity
  • Equivalence Partitioning
  • Error Guessing
  • Boundary Value Analysis
  • Traceability Matrix
  •  
    SDLC Models
     
  • Introduction
  • Waterfall Model
  • Iterative Model
  • V-Model
  • Spiral Model
  • Big Bang Model
  • RAD Model
  • Prototyping Model
  •  
    Software Testing Types
     
  • Static Testing
  • Dynamic Testing
  • Blackbox Testing
  • Whitebox Testing
  • Unit Testing
  • Requirements Testing
  • Regression Testing
  • Error Handling Testing
  • Manual support Testing
  • Intersystem Testing
  • Control Testing
  • Parallel Testing
  • Volume Testing
  • Stress Testing
  • Performance Testing
  • Agile Testing
  • Localization Testing
  • Globalization Testing
  • Internationalization Testing
  •  
    Test Plan
     
  • Introduction
  • Test Plan Development
  • Test Plan Template
  • Regional Differences
  • Criticism
  • Hardware Development
  • IEEE 829-1998
  • Testing Without a TestPlan
  •  
    Code Coverage
     
  • Introduction
  • Measures
  • Working
  • Statement Coverage
  • Branch Coverage
  • Path Coverage
  • Coverage criteria
  • Code coverage in practice
  • Tools
  • Features
  •  
    Quality Management
     
  • Introduction
  • Components
  • Capability Maturity Model
  • CMMI
  • Six Sigma
  •  
    Project Management
     
  • Introduction
  • PM Activities
  • Project Control Variables
  • PM Methodology
  • PM Phases
  • PM Templates
  • Agile PM
  •  
    Automated Testing Tools
     
  • Quick Test Professional
  • WinRunner
  • LoadRunner
  • Test Director
  • Silk Test
  • Test Partner
  • Rational Robot
  •  
    Performance Testing Tools
     
  • Apache JMeter
  • Rational Performance Tester
  • LoadRunner
  • NeoLoad
  • WAPT
  • WebLOAD
  • Loadster
  • OpenSTA
  • LoadUI
  • Appvance
  • Loadstorm
  • LoadImpact
  • QEngine
  • Httperf
  • CloudTest
  •  
    Languages
     
  • Perl Testing
  • Python Testing
  • JUnit Testing
  • Unix Shell Scripting
  •  
    Automation Framework
     
  • Introduction
  • Keyword-driven Testing
  • Data-driven Testing
  •  
    Configuration Management
     
  • History
  • What is CM?
  • Meaning of CM
  • Graphically Representation
  • Traditional CM
  • CM Activities
  • Tools
  •  
    Articles
     
  • What Is Software Testing?
  • Effective Defect Reports
  • Software Security
  • Tracking Defects
  • Bug Report
  • Web Testing
  • Exploratory Testing
  • Good Test Case
  • Write a Test
  • Code Coverage
  • WinRunner vs. QuickTest
  • Web Testing Tools
  • Automated Testing
  • Testing Estimation Process
  • Quality Assurance
  • The Interview Guide
  • Upgrade Path Testing
  • Priority and Severity of Bug
  • Three Questions About Bug
  •    
     
    Home » Testing Articles » Usablity Testing Articles » 8 guidelines for usability testing

    8 guidelines for usability testing

    A D V E R T I S E M E N T


    Introduction

    In professional web design circles, the usability testing session has become an essential component of any major project. Similar to focus groups in brand development and product launches, usability testing offers a rare opportunity to receive feedback from the very people the website is aimed at - before it's too late to do anything about it.

    But how can you get the most from these usability testing sessions?

    Choosing your subjects

    As with any market research project, the results will only be as good as the people you test. Do not test people from your own company, or friends and family. Go to a market research firm or temp agency and ask them to source participants to a certain profile. Make sure the market research firm does not provide the name of the company or any other details that will cloud the judgement of the participants.

    Before the usability testing

    As with everything in life, first impressions are vital. Each participant must be put at ease. Remember, the usability testing session is often an extremely artificial environment and, for the most beneficial and informative results, we want them to behave as if they were using the site at home or work.

    Provide clear instructions on how to get to the usability testing location, and if necessary meet the participants at local stations. Do not use terms such as 'usability testing' or 'market research', as these can confuse and put people on edge. Also, ensure that participants know how long the usability testing will take, and the type of tasks they will be expected to perform.

    After the initial greeting and welcoming drinks, there are always legal forms that must be signed. It is essential that these are written in plain English, and are as short as possible. The last thing any nervous usability testing subject wants is to be given a contract that looks like they're signing their soul away. All you want is for them to be reassured that the tests are completely confidential, and for permission to use the data generated during the test as part of our results. So, tell them that.

    Beginning the usability testing

    Before diving into key tasks, get the user familiar with the environment. Tell them the website's name and URL, and ask them for initial feedback on what they would expect from the site or what they would like the site to be. Make a note of any terms or phrases they use - this not only demonstrates you are taking their feedback seriously, but may provide useful tips to possible labels for key functionality or navigation.

    Next, let them look at the website they are testing. Gauge their first impressions before allowing them to familiarize themselves with the site.

    These few simple tasks will help convince the participant that the usability testing will not be difficult and, perhaps most importantly, that they're not the ones being tested.

    Choosing tasks

    Set tasks that are essential to the new site's success, such as:

    • Buying products
    • Paying bills
    • Contacting the client

    Remember, you're not looking for an ego massage. The site was built for a reason - can your target audience do what you need them to do?

    It's also a good idea to ask the user to suggest tasks. While this gives another indication of their expectations and requirements, it may suggest new functionality or priorities.

    How to word tasks

    People tend to perform more naturally if you provide them with scenarios rather than instructions. When giving them tasks, you should use phrases like 'Scenario A has occurred, and you need to ring the company urgently - find the telephone number'. This is far better than 'find the contact us section of the site'.

    Presenting tasks

    Only give participants one task at a time. More than this may intimidate them, or alter their approach to the test.

    If the user is required to use inputs from outside the test (e.g. an email giving them a password to the site), give them these inputs in the form they will be presented. This will provide useful feedback on all elements of the process, rather than simply the site.

    How to behave during the usability testing

    It's essential that you remember it's the website that is being tested, not you or the subject. Any feedback you get is valuable - make sure the participant knows this. If they can't do something, make sure they know it's not their fault.

    You must stay quiet and out of sight during the test. You must not alter the test results by providing clues, suggesting directions or by reacting to things they say or do. All feedback you give must be neutral. Do not start shaking your head or huffing, however tempting it might be!

    The only time you should speak is to help the participant give an opinion, or to clarify a response. If in doubt, shut up!

    Given the investment made in the project, clients often find it difficult to be quiet during tests. If your client wants to be present, put them in another room with an audio/video link.

    After the usability testing

    After all the tasks have been completed, you should gather as much information as possible. Asking for overall impressions of the site will allow you to judge whether the expectations have been met, and whether the participant's view of the client or site has changed during the process.

    Always ask for suggestions - this not only demonstrates the value you place on their thoughts, but may provide insights into how the site can better support the user.

    Finally, ask the participant what they remember about the site structure and functions of the site. Clear recollection will confirm that the site is structured logically and help identify any labeling issues you may have missed.



    More Usablity Testing Articles
    1 2 3 4 Next



    discussionDiscussion Center
    Discuss
    Discuss

    Query

    Feedback
    Yahoo Groups
    Y! Group
    Sirfdosti Groups
    Sirfdosti
    Contact Us
    Contact

    Looking for Software Testing eBooks and Interview Questions? Join now and get it FREE!
     
    A D V E R T I S E M E N T
       
       

    Members Login


    Email ID:
    Password:


    Forgot Password
    New User
       
       
    Testing Interview Questions
  • General Testing
  • Automation Testing
  • Manual Testing
  • Software Development Life Cycle
  • Software Testing Life Cycle
  • Testing Models
  • Automated Testing Tools
  • Silk Test
  • Win Runner
  •    
       
    Testing Highlights

  • Software Testing Ebooks
  • Testing Jobs
  • Testing Frequently Asked Questions
  • Testing News
  • Testing Interview Questions
  • Testing Jobs
  • Testing Companies
  • Testing Job Consultants
  • ISTQB Certification Questions
  •    
       
    Interview Questions

  • WinRunner
  • LoadRunner
  • SilkTest
  • TestDirector
  • General Testing Questions
  •    
       
    Resources

  • Testing Forum
  • Downloads
  • E-Books
  • Testing Jobs
  • Testing Interview Questions
  • Testing Tools Questions
  • Testing Jobs
  • A-Z Knowledge
  •    
    Planning
    for
    Study ABROAD ?


    Study Abroad


    Vyom Network : Free SMS, GRE, GMAT, MBA | Online Exams | Freshers Jobs | Software Downloads | Programming & Source Codes | Free eBooks | Job Interview Questions | Free Tutorials | Jokes, Songs, Fun | Free Classifieds | Free Recipes | Bangalore Info | GATE Preparation | MBA Preparation | Free SAP Training
    Privacy Policy | Terms and Conditions
    Sitemap | Sitemap (XML)
    Job Interview Questions | Placement Papers | SMS Jokes | C++ Interview Questions | C Interview Questions | Web Hosting
    German | French | Portugese | Italian