Chapter 11


1:

True or False: All software has a user interface and therefore must be tested for usability.

A1:

True. Eventually, even the most deeply embedded software is exposed, in some way, to a user. Keep in mind that the UI may be as simple as a switch and a light bulb or as complex as a flight simulator. Even if the software is a single module in a code library, its interface, in the form of variables and parameters, is exposed to a programmerwho can be a user, too.

2:

Is user interface design a science or an art?

A2:

It's a little bit of both. Many user interface designs have been thoroughly tested in the labs, been through rigorous studies, only to be complete failures in the marketplace.

3:

If there's no definitive right or wrong user interface, how can it be tested?

A3:

Software testers should check that it meets seven important criteria: That it follows standards and guidelines, that it's intuitive, consistent, flexible, comfortable, correct, and useful.

4:

List some examples of poorly designed or inconsistent UIs in products you're familiar with.

A4:

This answer will vary based on the products you use but think about these: Try setting the time on your car radio's clockcan you do it without using the manual?

Most Windows dialog boxes have the OK button on the left and the Cancel button on the right, whereas others have Cancel on the left and OK on the right. If you get used to one layout and click without looking, you could lose your work!

Did you ever accidentally hang up on someone when you clicked the receiver hook on your phone to use call waiting or conference calling?

And, the best one of all time…is up to you to find!

5:

What four types of disabilities could affect software usability?

A5:

Visual, hearing, motion, and cognitive impairments.

6:

If you're testing software that will be accessibility enabled, what areas do you need to pay close attention to?

A6:

Areas dealing with the keyboard, mouse, sound, and display. If the software was written to a popular platform that supports accessibility, the test effort will be a bit easier than if the accessibility features were programmed entirely from scratch.



    Software Testing
    Lessons Learned in Software Testing
    ISBN: 0471081124
    EAN: 2147483647
    Year: 2005
    Pages: 233

    flylib.com © 2008-2017.
    If you may any questions please contact us: flylib@qtcs.net