|
|
1. FUNCTIONALITY
1.1 LINKS
1.1.1 Check that the
link takes you to the
page it said it would.
1.1.2 Ensure to have no
orphan pages (a page
that has no links to it)
1.1.3 Check all of your
links to other websites
1.1.4 Are all referenced
web sites or email
addresses hyperlinked?
|
1.1.5 If we have removed
some of the pages from
our own site, set up a
custom 404 page that
redirects your visitors
to your home page (or a
search page) when the
user try to access a
page that no longer
exists.
1.1.6 Check all mailto
links and whether it
reaches properly
1.2 FORMS
1.2.1 Acceptance of
invalid input
1.2.2 Optional versus
mandatory fields
1.2.3 Input longer than
field allows
1.2.4 Radio buttons
1.2.5 Default values on
page load/reload(Also
terms and conditions
should be disabled)
1.2.6 Is Command Button
can be used for
HyperLinks and Continue
Links ?
1.2.6 Is all the datas
inside combo/list box
are arranged in
chronolgical order?
1.2.7 Are all of the
parts of a table or form
present? Correctly laid
out? Can you confirm
that selected texts are
in the "right place?
1.2.8 Does a scrollbar
appear if required?
1.3 DATA VERIFICATION
AND VALIDATION
1.3.1 Is the Privacy
Policy clearly defined
and available for user
access?
1.3.2 At no point of
time the system should
behave awkwardly when an
invalid data is fed
1.3.3 Check to see what
happens if a user
deletes cookies while in
site
1.3.4 Check to see what
happens if a user
deletes cookies after
visiting a site
2. APPLICATION
SPECIFIC FUNCTIONAL
REQUIREMENTS
2.1 DATA
INTEGRATION
2.1.1 Check the maximum
field lengths to ensure
that there are no
truncated characters?
2.1.2 If numeric fields
accept negative values
can these be stored
correctly on the
database and does it
make sense for the field
to accept negative
numbers?
2.1.3 If a particular
set of data is saved to
the database check that
each value gets saved
fully to the database.
(i.e.) Beware of
truncation (of strings)
and rounding of numeric
values.
2.2 DATE FIELD CHECKS
2.2.1 Assure that leap
years are validated
correctly & do not cause
errors/miscalculations.
2.2.2 Assure that Feb.
28, 29, 30 are validated
correctly & do not cause
errors/ miscalculations.
2.2.3 Is copyright for
all the sites includes
Yahoo co-branded sites
are updated
2.3 NUMERIC FIELDS
2.3.1 Assure that lowest
and highest values are
handled correctly.
2.3.2 Assure that
numeric fields with a
blank in position 1 are
processed or reported as
an error.
2.3.3 Assure that fields
with a blank in the last
position are processed
or reported as an error
an error.
2.3.4 Assure that both +
and - values are
correctly processed.
2.3.5 Assure that
division by zero does
not occur.
2.3.6 Include value zero
in all calculations.
2.3.7 Assure that upper
and lower values in
ranges are handled
correctly. (Using BVA)
2.4 ALPHANUMERIC
FIELD CHECKS
2.4.1 Use blank and
non-blank data.
2.4.2 Include lowest and
highest values.
2.4.3 Include invalid
characters & symbols.
2.4.4 Include valid
characters.
2.4.5 Include data items
with first position
blank.
2.4.6 Include data items
with last position
blank.
Interface, Error Handling
and Compatibility -> Next
Page
|
