Testing application on web User Interface Tests

Testing application on web User Interface Tests TOPICS COVERED IN THIS CHAPTER Introduction User Interface Design Testing User Interface Implementation Testing Usability and Accessibility Testing Testing Considerations Bibliography and Additional Resources

Seminar for Testing.

Book: Testing application on web

Chapter 10: User Interface Tests

• Lecturer : Nguyen Dang Khoa

• Team members:

– Nguyen Nhat Tien 07520358

– Phan Thanh Huy 09520106

– Tran Le Trung Hieu 09520085

– Pham Anh Duong 09520047

– Tran Minh Quang 09520225

TOPICS COVERED IN THIS CHAPTER

1 Introduction

2 User Interface Design Testing

3 User Interface Implementation Testing

4 Usability and Accessibility Testing

5 Testing Considerations

6 Bibliography and Additional Resources

1 Introduction

• two primary classes of UI testing issues:

– (1) the design of UI components.

– (2) the implementation of UI components.

User Interface Design Testing

• Subjective impressions of “ease of use” and

“look and feel”

• Suitability of all aspects of the design

• Consistent aesthetics, feedback, and

interactivity directly affect an application’s usability

2 User Interface Design Testing

• Profiling the Target User: Gaining an understanding

of a Web application’s target user is central to

evaluating the design of its interface Without

knowing the user’s characteristic sand needs, you

cannot accurately assess how effective the UI design is.

• Considering the Design: The second step in preparing for UI design testing is to study the design employed

by the application Different application types and

target users require different designs.

Profiling the Target User

• Computer Experience: How long have the

intended users been using a computer? Do they use a computer professionally or only casually at home? What activities are they

typically involved with? What assumptions does the SUT make about user skill level, and how well do the expected users’ knowledge and skills match those assumptions?

Profiling the Target User

• Web Experience: How long have the users

been using the Web system? Web systems

occasionally require client-side users to

configure browser settings Therefore, some experience with Web browsers will be helpful

Profiling the Target User

• Domain Knowledge: Are users familiar with the subject matter associated with the

application?

Profiling the Target User

• Application-Specific Experience: Will users be familiar with the purpose and capabilities of the program because of past experience? Is this the first release of the product, or is there

an existing base of users in the marketplace who are familiar with the product?

Considering the Design

• Design Approach

• User Interaction (Data Input)

• Data Presentation (Data Output)

Design Approach

• Design metaphors are cognitive bridges that can help users understand the logic of UI flow

by relating them to experiences that users

may have had in the real world or in other

places

User Interaction (Data Input)

• User Interface Controls

• Feedback and Error Messages

• Dynamic User Interface Controls

• Navigation Methods

• Mouse/Keyboard Action Matrices

User Interaction (Data Input)

User interface controls:

User interface controls are graphic objects that enable users to interact

with applications.

Feedback and Error Messages

• Consistency in audible and visible feedback is essential for maintaining clear communication between users and applications

• Error messaging in particular should be

evaluated for clarity and consistency.

• You can identify commonly accepted

guide-lines within each computing platform for

standard placement of UI elements

Two types of message-based feedback are available Figure 10.14 illustrates a typical client-based error message (generated by error-

checking JavaScript on the client-side) that utilizes a browser-based message box Figure

10.15 shows typical server-based feedback.

• Some errors to look for include the following:

• Displaying incorrect error message for the condition.

• Missing error messages

• Poorly worded, grammatically incorrect, and misspelled errors

• Messages were not written for the user and, therefore, are not useful to the user For example,

“Driver error 80004005.”

• Error message is not specific nor does it offer a plausible solution

• Similar errors are handled by different error messages

• Unnecessary messages distract users

• Inadequate feedback or error communication to users

• Handling methods used for similar errors are not consistent.

Dynamic user interface controls

HTML mutilmedia tags : Java applet, ActiveX, Script

 Scripts: Scripts are embedded into HTML

•HTML code with <SCRIPT> tags

• Using Client-side scripts

•JavaScripts produced by netscape, JsScript VBScript

 Java: Produced by SUN

•A Java programming can run opera system diffirent

•Java ensure better security protection for client users

 Active X: runs within ActiveX-enabled browsers

•Easy creare app and features-rich app

•Dependent on the Win-dows platform

Some UI control errors

 The default state of UI control is incorrect

 The updated state of UI control is incorrect

 The default input value is incorrect

 The dialog box is too wide or long (800x600)

 Set View Text Size to the Largest and the Smallest

 Check for ALT attributes

 Invalid inputs are not detected and handled at client-side

 Invalid inputs are not detected and handled at server-side

 Scripts, CSS, Java applets, and ActiveX controls errors among different releases of browser

• apps will function at some capacity or will simply stop

Navigation Methods

• Navigation methods dictate how users

navigate through a Web application or Web

pages, from one UI control to another within the same page (screen, window, or dialog box) and from one page to the next

• What do I test here?

What do I test here?

• Is the application’s navigation intuitive?

• How well is information presented to the

user?

• Look at the keyboard shortcuts that are

supported Are they functioning?

• Have the navigation features been tested for accessibility?

•

Mouse/Keyboard Action Matrices

• Mouse action: click, drag, drop

• Key board: key press, spiecial key

• What do I test here?

Data Presentation (Data Output)

Data Presentation (Data Output)

Web

App UI Controls: menus, buttons, etc. User

HTML page h

Frames, tables, etc.

Create

Figures 10.16, 10.17, and 10.18 illustrate three data presentation views that are available in the sample application Each view conveys the same data through a different template built using HTML frames and tables.

There are at least three types of potential errors:

3 User Interface Implementation Testing

User Interface Implementation Testing

Development

Features Fail

Pass

UI design testing

simultaneously

UI control does not operate as designed

4 Usability and Accessibility Testing

Usability and Accessibility Testing

• Depend software testing organization

• How dose appliacation usability?

• Is it easy to learn?

• What do I test here?

What do I test here?

• How easy will it be for a user who has never

seen the product before to carry out basic tasks?

• How easy will it be for a user who has used the product before to remember how to carry out the same tasks?

• How good is the user’s experience in using the product?

•

5 Testing Considerations

USER INTERACTION TESTING CONSIDERATIONS

• How is information presented to the user?

• Is there a central workspace? If so, does it remain consistent from screen to screen?

• Is data presented in frames? If so, is there a choice for nonframe browsers?

• Are data manipulation methods presented

intuitively and consistently?

• Is drag-and-drop functionality supported?

•

UI CONTROL TESTING CONSIDERATIONS

• What are the UI controls used by the application under test: dialog boxes, radio buttons, drop-down menus?

• Are the layout and implementation of UI controls intuitive and consistent throughout the application?

• Do data interaction methods vary illogically from screen

to screen (drag-and-drop, text entry, queries, etc.)?

• Are properties consistently applied to all HTML elements?

• Do command buttons perform the actions they purport to?

•

6 Bibliography and Additional Resources

• Jeffrey Rubin, John Wiley & Sons, Inc (1994).

• Microsoft Windows User Experience (Microsoft Professional

Editions), by Microsoft

• Corporation, Microsoft Press (1999).

• Web Style Guide: Basic Design Principles for Creating Web Sites by Patrick J Lynch

• and Sarah Horton, Yale University Press (1999).

Thank for listening!