Sie sind auf Seite 1von 7

1.

CONCEPTUAL ELEMENTS TESTING


(FOrm, BackGround)

Check that general screen background has the correct color.

Check that tooltip has the correct color.

Check the fields backgrounds have the correct color.

Check that design displaying isnt depended on different screen resolutions.

Check that in read-only mode the field backgrounds have correct color.

Check that text in all fields is specified in the correct screen font.

Check that all the field prompts aligned perfectly on the screen.

Check that all field edit-boxes aligned on the screen.

Check that all group-boxes aligned correctly on the screen.

Do elements positions change while the screen is resizable?

Check that all field prompts spelt correctly.

Check that all character or alpha-numeric fields left justified. This is the default
unless otherwise specified.

Check that all error message text spelt correctly on the page.

Check that all user input captured in upper or lower case consistently?

Assure that all required fields are marked with special color/symbol (asterix).

Ensure all fields are disabled in read-only mode.

Assure that all windows have a consistent and identical look and feel.

Assure that all dialog boxes have a consistent and identical look and feel.

Check that cursor positioned in the first input field or control when the page is
opened.

1.2

VALIDATION TESTING

Check that a failure of validation on every field causes a logical user error
message.

Check that all fields edit boxes indicate the number of characters they will hold by
their length e.g. a 30 character field should be a lot longer.

Check that format of error messages is standard for all pages.

Check that the user is required to fix entries which have failed validation tests.

Check that any fields got multiple validation rules and if so that all rules are being
applied.

Check that entered invalid value is the invalid entry identified. The field and its
value are highlighted correctly with an error message.

Check that validation consistently is displayed on the page at the same logical
zone (e.g. in the bottom/on the top of page form or under the each field ).

For all numeric fields check the minimum and maximum values and also some
mid-range values allowable.

For all character/alphanumeric fields check the field to ensure that there is a
character limit specified and that this limit is exactly correct for the specified
database size.

Check that all required fields require user data input.

1.3

NAVIGATION CONDITIONS

Can all pages be accessed correctly from the applications menu?

Can all pages be accessed correctly by clicking on links of applications pages?

Check that cursor type is changed in dependence on link it on not (hand for links/
arrow for other elements)

Check that color of clicked link was changed to specify one.

Check that bread crumbs are used in application on every page except Home page

Check that breadcrumbs correctly show people their current location relative to
higher-level concepts.

Check that breadcrumbs afford one-click access to higher site levels.

Check that name of breadcrumbs agrees with page name.

1.4

TABLE TESTING

Check that table has a paging: current page/next/previous/to the first/last page.

Check that sorting by columns name is designed obviously for users.

Check that default data sort in the table is ascending.

Check that table data dont expand the tables boards.

Check that all information is displayed in the table in case of windows size
changing.

1.5

NUMERIC FIELDS TESTING

Assure that lowest and highest values are handled correctly

Assure that invalid values are logged and reported

Assure that valid values are handles by the correct procedure

Assure that numeric fields with a blank in position 1 are processed or reported as
an error

Assure that fields with a blank in the last position are processed or reported as an
error

Assure that both + and - values are correctly processed

Assure that division by zero does not occur

Include value zero in all calculations

Include at least one in-range value

Include maximum and minimum range values

Include out of range values above the maximum and below the minimum

Assure that upper and lower values in ranges are handled correctly

1.6

ALPHA FIELDS TESTING

Use blank and non-blank data

Include lowest and highest values

Include invalid characters & symbols

Include valid characters

Include data items with first position blank

Include data items with last position blank

1.7

DATE FIELD TESTING

Assure that leap years are validated correctly & do not cause
errors/miscalculations

Assure that month code 00 and 13 are validated correctly & do not cause
errors/miscalculations

Assure that 00 and 13 are reported as errors

Assure that day values 00 and 32 are validated correctly & do not cause
errors/miscalculations

Assure that Feb. 28, 29, 30 are validated correctly & do not cause
errors/miscalculations

Assure that Feb. 30 is reported as an error

Assure that century change is validated correctly & does not cause
errors/miscalculations

Assure that out of cycle dates are validated correctly & do not cause
errors/miscalculations

1.8

RADIO BUTTONS AND CHECKBOXES


TESTING

Check that radio buttons are used when there is a list of two or more options that
are mutually exclusive and the user must select exactly one choice. Clicking a
non-selected radio button will deselect whatever other button was previously
selected in the list.

Ensure that checkboxes are used when there are lists of options and the user may
select any number of choices, including zero, one, or several. Each checkbox is
independent of all other checkboxes in the list, so checking one box doesn't
uncheck the others.

Check that a stand-alone checkbox is used for a single option that the user can
turn on or off.

Check that checkbox is a small square that has a checkmark or an X when


selected. And a radio button is a small circle that has a solid circle inside it when
selected. This is the default unless otherwise specified.

Check that lists lay out vertically, with one choice per line. If user must use a
horizontal layout with multiple options per line, make sure to space the buttons
and labels so that it's abundantly clear which choice goes with which label. In the
following list, for example, it's difficult to see the correct radio button to click for
option four.

Check that for checkbox labels are used positive and active wording, so that it's
clear what will happen if the user turns on the checkbox. In other words, avoid
negations such as "Don't send me more email," which would mean that the user
would have to check the box in order for something not to happen.

Check that a default selection is always offered for radio button lists. By
definition, radio buttons always have exactly one option selected, and you
therefore shouldn't display them without a default selection. (Checkboxes, in
contrast, often default to having none of the options selected.)

Check that checkboxes and radio buttons are used only to change settings, not as
action buttons that make something happen. Also, the changed settings should not
take effect until the user clicks the command button (labeled "OK" for example,
or "Proceed to XXX" where "XXX" is the next step in a process).

1.9

TABS TESTING

Check that in the application tabs are used to alternate between views within the
same context (not to navigate to different areas).

Check it logically chunks the content behind the tabs so users can easily predict
what they'll find when they select a given tab. (If you don't find clearly distinct
groupings, then tabs are likely the wrong interface control for managing your
content.)

Check that tabs are parallel in nature. This is the default unless otherwise
specified.

Check that the currently selected tab is highlighted. Here, it's highlighted by its
lack of color, which works fine as long as there are at least 3 tabs. (With only 2
tabs, it would be harder to tell which one was selected.)* In addition to
highlighting, the current tab may be marked by size, a boldfaced label, an icon, or
by making it appear to be in front of the other tabs.

Check that the unselected tabs are clearly visible and readable, reminding the user
of the additional options. If the non-highlighted tabs are faded too much into the
background, there's a risk that users will never click them and never discover the
many hidden features.

Check that the labels are short and use plain language, rather than made-up terms.
Tab labels should usually be 1-2 words. Short labels are more scannable.

Check that switching to tabs is a rather fast action (ideally <0.1 s) that people feel
there's a physical connection between their mouse click and the appearance of the
chosen panel. Fast response time ensures that clicking a new tab immediately
brings the corresponding panel to the front. This is probably achieved through
AJAX, but the programming technique is not important.

Check that changes on the tab was saved in spite of switching to other tabs. User
makes changes on the first tab and switch to other tabs, then returns to the first tab
and sees the last modified information.

1.10 DESIGN OF EMAILS FROM THE SITE


TESTING

Check that emails from site are structured and displayed without html tags.

Check that email design is corresponded to the whole site design.

Check that email has a topic and signature.

Check that sender (From) is obviously understandable.

Check that links from email may be correctly opened.

Check that images if any are displayed in the email.

1.11 SEARCH TESTING

Check that for user to understand search isnt challenging (users confuse
logical and/or mental models of search can vary).

Check that search field is placed on top of page.

Check that results display search criteria.

Check that results of search is not case-sensitive (Searching word: Tsesna;


Results include: TSESNA, tsesna, Tsesna etc.)

Check that search works properly if user perform a search with the wildcards
* and ?.

1.12 InternationlizaTION TESTING

Check that localization is obvious and accessible for users selection (flags/
visible open lists of languages).

Das könnte Ihnen auch gefallen