User Interface Testing explian each one with example ? (web app) Interface featu

Question

User Interface Testing

explian each one with example ? (web app)

Interface features are tested to ensure that design rules,
aesthetics, and related visual content is available for the
user without error.
Individual interface mechanisms are tested in a manner
that is analogous to unit testing.
Each interface mechanism is tested within the context of a
use-case or NSU for a specific user category.
The complete interface is tested against selected usecases
and NSUs to uncover errors in the semantics of the
interface.
The interface is tested within a variety of environments
(e.g., browsers) to ensure that it will be compatible.

Explanation / Answer

Interface features are tested to ensure that design rules,
aesthetics, and related visual content is available for the
user without error.

UI is meant to be look beautiful. Though all content is correct, the way UI shows it to user may effect user attention. This is something related to non-functional user requirements. Proper CSS, fonts, color coding schemes etc should used. it should be tetsed from User point of view. testing of screens one by one. no parts of screen should not overlap on each other etc.

Individual interface mechanisms are tested in a manner
that is analogous to unit testing.
A screen may contain many UI controls such as testboxes, buttons, dropdowns, links, images etc. Each UI component will have some functionality. So, Each component needs to be tested to ensure that at unit level its working fine.
Ex : various buttons. simple Submit and cancel buttons. Upon clicking on 'submit', form should be submitted to server and upon cancel it should submit and should exit from that screen and go to normal landing screen(depends on app behaviour).

Each interface mechanism is tested within the context of a
use-case or NSU for a specific user category.
Ans : UI some times acts differently for different users. So, UI needs to be tested for each use case for at least one user from each specific user category.
Ex : in same UI, if user logged in Administrator, he should have some more features for him to do his admin related activities. The same shouldn't be available for other user categories.
Ex : same Application page/screen looks different if viewed without logging to system and after logging to system.

All these scenarios needs to be tested

The complete interface is tested against selected usecases
and NSUs to uncover errors in the semantics of the
interface.
Ans : A use case is a series of related interactions between a user (or more generally, an “actor”) and a system that enables the user to achieve a goal. As defination says, each use case is a series of actions user performs(clicking buttons/entering some text etc). So, for each test case from start screen to end screen testing is required.
Ex : consider composing mail in Gmail. sequential steps are
- clicking on compose mail
- add receipient ids to TO field
- add receipient ids to Cc field if required followed BCC
- Enter body of gmail
- add attachments if any. UI should what attached.
- click on send

this is one use case. it needs to be tested completely.

The interface is tested within a variety of environments
(e.g., browsers) to ensure that it will be compatible.

Ans : UI is mostly browser dependent. UI may work properly in a browser like Chrome but it may won't work browser like Internet Explorer. This is called browser Compatability. So, all features of APP UI should tested in different browser to make sure it works as expected.

Related Questions

Navigate

• Browse (All)
• Browse U
• Subjects

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.