GENERIC TEST CASES GUIDELINE

FORM OBJECTS - TEXT BOX

VALIDATE IF LEADING SPACES ARE ENTERED IN A ALPHANUMERIC FIELD, THE SAME IS TRIMMED BEFORE SAVING THE RECORD.
VALIDATE IF TRAILING SPACES ARE ENTERED IN A ALPHANUMERIC FIELD, THE SAME IS TRIMMED BEFORE SAVING THE RECORD.
VALIDATE IF ONLY SPACES ARE ENTERED THE SAME IS NOT ALLOWED TO BE SAVED
VALIDATE IF ANY PRIMARY KEY FIELD THAT IS GOING TO BE DISPLAYED IS NOT CASE SENSITIVE
VALIDATE IF FIELD LENGTH IS 20 AND DATA ENTERED IS 12 SPACES + 12 CHARACTERS. THE RECORD IS NOT SAVED.
ENTER VALID DATA WITHIN THE SPECIFIED RANGE
ENTER THE LEAST NUMBER OF CHARACTERS AS DEFINED BY THE WIDTH
ENTER THE MAXIMUM NUMBER OF CHARACTERS AS DEFINED BY THE WIDTH
ENTER NUMBER OF CHARACTERS WHICH EXCEEDS THE WIDTH
ENTER DATA SURROUNDED BY SINGLE QUOTES
ENTER DATA SURROUNDED BY DOUBLE QUOTES
VALIDATE IF MORE SPACES ARE ENTERED BETWEEN TWO STRINGS IN A ALPHANUMERIC FIELD, THE SAME IS TRIMMED BEFORE SAVING THE
RECORD.
ENTER VALUE WITH SINGLE QUOTE AND '&' AND VALUES LIKE ~!@#$%^&*()_
VERIFY CUT/COPY/PASTE IS SUPPORTED IN THE TEXT FIELD
FORM OBJECTS - NUMERIC FIELD
VALIDATE FOR BOUNDARY CONDITIONS IN NUMERIC FIELDS.
VALIDATE IF NEGATIVE NUMBERS IS NOT ACCEPTABLE IN NUMERIC FIELDS WHICH SHOULD EXPECT POSITIVE NUMBERS.
VALIDATE IF ANY VALUE IS BEING DISPLAYED FOR NUMERIC DATA, THE SAME IS DISPLAYED ALONG WITH TWO DECIMAL PLACES UNLESS IT IS
SYSTEM SPECIFIC. FOR E.G.: RS. 147 SHOULD BE DISPLAYED AS RS. 147.00
ENTER A VALID NUMBER WITHIN THE SPECIFIED RANGE
ENTER THE LOWEST NUMBER
ENTER THE HIGHEST NUMBER
ENTER A RATIONAL NUMBER (FRACTION) E.G., 2/5
ENTER A NEGATIVE RATIONAL NUMBER (FRACTION) E.G. -2/5
ENTER A SPACE IN THE FIRST POSITION AND THEN THE NUMBER
ENTER A SPACE IN THE LAST POSITION AND THEN THE NUMBER
ENTER NON NUMERIC VALUES LIKE !@#$%^&*()_
TOOL BAR
THE TOOLBAR BUTTONS REQUIRE ONLY A SINGLE MOUSE CLICK TO ACTIVATE.
THERE IS AN EQUIVALENT MENU ITEM FOR EVERY TOOLBAR BUTTON.
ALL TOOLBAR BUTTONS SHOULD BE PROVIDED WITH A LABEL OR TOOL TIP.
TOOLBAR BUTTONS ARE INITIALLY PLACED IN THE TOOLBAR AND THEN THE BUTTONS ARE ACTIVATED/DEACTIVATED WHEN APPROPRIATE.

FORM OBJECTS - LIST BOX

VALIDATE IF THE CONTENTS OF THE LIST BOXES IN THE SYSTEM ARE SORTED IN ASCENDING ORDER.
VALIDATE IF THE CONTENT SORTING IN THE LIST BOXES IS NOT CASE-SENSITIVE. I.E. THE LIST SHOULD DISPLAY 'A' BEFORE 'A' AND 'A' BEFOR
'Z'.
VALIDATE IF THE LIST BOXES HAVE 'ALL' OR 'PLEASE SELECT' OPTION AS REQUIRED.
ENTER A VALUE IN THE DROP DOWN / LIST BOX
SELECT A VALUE WITH THE MOUSE
SELECT A VALUE WITH THE KEYBOARD
SELECT MULTIPLE ITEMS FROM THE LIST BOX
SCROLL BAR TO APPEAR AUTOMATICALLY, IF THERE ARE MORE THAN 8 ITEMS IN THE LIST BOX
THE WIDTH TO EXPAND AUTOMATICALLY TO ACCOMMODATE THE LONGEST WORD/SENTENCE
DEFAULT SELECTION
VERIFY THAT OLD VALUE IS RETAINED WHEN USER ACTION/INPUT IS INVALID
RADIO/OPTION BUTTON
ALL RADIO BUTTONS HAVE TEXT LABELS MENTIONING THE ESSENCE OF THE BUTTON.
USERS SHOULD NOT BE ABLE TO SELECT MORE THAN ONE RADIO BUTTON IN A GROUP.
SELECT A BUTTON WITH THE MOUSE

SELECT A BUTTON WITH THE KEYBOARD USING SPACE BAR

FORM OBJECTS - TEXT AREA
ENTER VALID DATA WITHIN THE SPECIFIED RANGE
ENTER THE LEAST NUMBER OF CHARACTERS AS DEFINED BY THE WIDTH
ENTER THE MAXIMUM NUMBER OF CHARACTERS AS DEFINED BY THE WIDTH
ENTER MORE NUMBER OF CHARACTERS WHICH EXCEEDS THE WIDTH
ENTER DATA WITH BLANK IN FIRST POSITION
ENTER DATA WITH A BLANK IN THE LAST POSITION
ENTER DATA SURROUNDED BY SINGLE QUOTES
ENTER DATA SURROUNDED BY DOUBLE QUOTES
SCROLL BAR APPEARANCE, VERTICAL AND HORIZONTAL SHOULD APPEAR WHEN THE VISIBLE AREA IS FILLED WITH DATA.
FORM OBJECTS- CHECKBOX
ALL CHECKBOXES MUST HAVE TEXT LABELS MENTIONING THE ESSENCE.
ABLE TO CHECK/UNCHECK USING MOUSE CLICK
ABLE TO CHECK/UNCHECK USING SPACE BAR
FORM OBJECTS - DATE FIELD
VALIDATE IF THE DATE DISPLAYED IS IN STANDARD FORMAT OF THE SYSTEM. FOR EG:DD/MM/YYYY
DATE FIELDS SHOULD CONTAIN A CALENDAR POPUP.
DATE FIELDS SHOULD TAKE THE FORMAT BASED ON THE LOCALIZATION.
DATE FIELD WILL CONTAIN AN ICON THAT IS UNIQUELY IDENTIFIED THROUGH OUT THE DATE FIELDS.
ASSURE THAT LEAP YEARS ARE VALIDATED
ASSURE THAT OLD VALUE IS RETAINED WHEN MONTH VALUE IS 0 AND ABOVE 12
ASSURE THAT DAY VALUES 0 AND ABOVE THE LAST DAY OF THE MONTH ARE UPDATED WITH THE LAST DAY OF THE MONTH
IF THERE ARE OTHER DATES ON THE SAME RECORD, CHECK IF THEY ACCEPT THE VALUES WHICH DOESNT BREAK THE FUNCTIONALITY.
EXAMPLE END DATE SHOULD BE >= START DATE
ASSURE THAT OUT OF CYCLE DATES ARE VALIDATED CORRECTLY & DO NOT CAUSE ERRORS/MISCALCULATIONS.
VERIFY THAT THE OLD VALUE IS RETAINED WHEN USER ACTION/INPUT IS INVALID
VALIDATE WITH ALL POSSIBLE DATE FORMATS.
VALIDATE WITH ALL POSSIBLE TIME FORMATS.
LOCALIZATION / GLOBALIZATION TESTING
VERIFY DIFFERENT REGIONAL SETTINGS
ENTER LOCALIZED DATA INTO TEXT FIELDS
VERIFY DIFFERENT DATE FORMATS
VERIFY DIFFERENT CURRENCY FORMATS
VERIFY FIELD LENGTHS ARE NOT TRUNCATING VALUES
VERIFY LOCALIZED FIELD LABELS ARE NOT BEING TRUNCATED
ENTER DATA OF DOUBLE BYTE (UTF-16) CHARACTERS WHEN THE DATABASE COLUMN HOLDS DATA IN UNICODE FORMAT. ALSO WHEN THE
REQUIREMENT IS OF ONLY UTF-8
VERIFY THE CONTENT BEING DISPLAYED FOR MIXED LANGUAGES IF THE APPLICATION IS INDEPENDENT OF BROWSER SETTINGS
PASSWORD FIELD TEST CASES
VALIDATE IF THE PASSWORD FIELD IS LEFT BLANK AND RECORD IS SAVED
VALIDATE IF THE RE- ENTER PASSWORD FIELD IS LEFT BLANK AND RECORD IS SAVED.
VALIDATE FOR ACCEPTANCE OF LEADING SPACES IN THE PASSWORD FIELD, THE SAME ARE SAVED.
VALIDATE FOR ACCEPTANCE OF TRAILING SPACES IN THE PASSWORD FIELD, THE ARE SAVED.
VALIDATE IF ONLY SPACES ARE ALLOWED TO BE SAVED IN THE PASSWORD FIELD
VALIDATE IF ONLY QUOTES ARE ALLOWED TO BE SAVED IN THE PASSWORD FIELD
VALIDATE WHETHER LEADING SPACES IN THE RE- ENTER PASSWORD FIELD ARE SAVED.
VALIDATE WHETHER TRAILING SPACES IN THE RE-ENTER PASSWORD FIELD ARE SAVED.
VALIDATE IF ONLY SPACES ARE ALLOWED TO BE SAVED IN THE RE-ENTER PASSWORD FIELD
VALIDATE IF ONLY QUOTES ARE ALLOWED TO BE SAVED IN THE RE-ENTER PASSWORD FIELD
VALIDATE IF RE-ENTER PASSWORD AND PASSWORD FIELDS CONTAIN DIFFERENT DATA

VALIDATE IF RE-ENTER PASSWORD AND PASSWORD FIELDS CONTAIN SAME DATA BUT DIFFERENT CASES(AS IN ONE IS CAPITAL AND OTHER IS
SMALL CASE)
EMAIL ID FIELD TEST CASES
VALIDATE IF AT LEAST ONE @ AND '.' ARE PRESENT IN EMAIL ID FIELD
VALIDATE IF SPACES TRIMMED IN THE BEGINNING AND END OF EMAIL ID FIELD
VALIDATE IF ONLY SPACES ALONG WITH @ AND . IS NOT ALLOWED TO BE SAVED IN EMAIL ID FIELD
VALIDATE IF EMAIL ID FIELD IS UNIQUE FOR A RECORD DEPENDING ON THE USABILITY.
VALIDATE IF EMAIL ID FIELD IS CASE INSENSITIVE
VALIDATE IF EMAIL ID FIELD ACCEPTS QUOTES
VALIDATE DUPLICATE EMAIL ID FOR A SPECIFIC DOMAIN.
PARAMETER SCREEN & REPORTS TEST CASES
VALIDATE FOR BLANK INPUTS IN THE FROM RANGE FIELD IS ACCEPTABLE.
VALIDATE FOR BLANK INPUTS IN BOTH FROM RANGE FIELD AND TO RANGE FIELD IS ACCEPTABLE
VALIDATE FOR BLANK INPUTS IN TO RANGE FIELD IS ACCEPTABLE.
VALIDATE IF VALUE IN TO RANGE FIELD IS SMALLER THAN FROM FIELD IS NOT ACCEPTABLE.
VALIDATE IF DATE RANGE FIELD DISPLAYS MAXIMUM VALUE PROVIDED IN SELECTION BOX IN 'TO' DATE FIELD AND MINIMUM VALUE IN THE
FROM DATE FIELD. AS PER THE REQUIREMENT OF THE QUERY.

VALIDATE IF BLANK SCREEN IS SUBMITTED THEN ALL THE RECORDS ARE DISPLAYED.
VALIDATE IF THE RESULT PAGE DISPLAYS THE NO. OF RECORDS FOUND FOR THE QUERY.
VALIDATE IF THE RESULT PAGE DISPLAYS NEW QUERY LINK TO GO BACK TO THE QUERY PAGE
VALIDATE IF STANDARD NO. OF RECORDS IS DISPLAYED ON A SINGLE RESULT PAGE OF THE REPORT.
VALIDATE IF THE BUTTON ON THE PARAMETER SCREEN IS LABELED AS 'SEARCH'.
VALIDATE IF NEXT AND PREVIOUS BUTTONS ARE PRESENT ON A PAGE, THE SAME IS LABELED AS 'NEXT' AND 'PREV' AND IS POSITIONED ON TH
RIGHT HAND SIDE AND LEFT HAND SIDE OF THE SCREEN RESPECTIVELY.
VALIDATE IF THE ALPHANUMERIC DATA & LABELS DISPLAYED IN THE REPORT IS LEFT ALIGNED.
VALIDATE IF THE NUMERIC DATA & LABELS DISPLAYED IN THE REPORT IS RIGHT ALIGNED.
VALIDATE IF THE NUMERIC DATA & LABELS REPRESENTING ID FIELDS OR LINKS IS DISPLAYED AS LEFT ALIGNED.
MULTI-USER TEST CASES
SUBMISSION OF A FORM FROM TWO DIFFERENT MACHINES
VALIDATE IF THE TWO DIFFERENT USERS ACCESS THE SAME RECORD FROM DIFFERENT MACHINES.
VALIDATE IF THE SAME USER IS ALLOWED TO ACCESS THE SAME RECORD FROM DIFFERENT MACHINES.
VALIDATE IF IN CASE OF MULTI-USER OPERATIONS, IF ANY UNIQUE KEY OR PRIMARY KEY IS VIOLATED, APPROPRIATE ERROR MESSAGE IS
SHOWN TO ONE OF THE USER.

VALIDATE FOR THE CHANGES IN MASTER DATA, WHEN THE SAME IS BEING USED IN THE TRANSACTION FROM THE OTHER TERMINAL
VALIDATE IF TWO DIFFERENT USERS TRY TO DELETE SAME RECORD FROM DIFFERENT MACHINES. (VALIDATE IF A USER TRY TO DELETE SAME
RECORD FROM DIFFERENT BROWSERS.
LOGIN RELATED TEST CASES
VALIDATE FOR SUBMISSION OF BLANK LOGIN SCREEN.
VALIDATE FOR CANCELLATION ON BLANK LOGIN SCREEN.
VALIDATE FOR THE FOCUS ON THE FIRST TEXT FIELD IN THE LOGIN SCREEN AFTER INVOKING THE SCREEN
VALIDATE FOR THE FOCUS ON THE LOGIN BUTTON IN THE LOGIN SCREEN AFTER INVOKING THE SCREEN
VALIDATE FOR SIMULTANEOUS LOGGING OF DIFFERENT TYPES OF USERS WITH THE SAME USER NAME AND PASSWORD.
VALIDATE IF THE USER NAME FIELD IS LEFT BLANK AND USER CLICKS ON LOGIN
VALIDATE IF THE PASSWORD FIELD IS LEFT BLANK AND USER CLICKS ON LOGIN.
VALIDATE IF AFTER CHANGING THE PASSWORD AND SAVING THE RECORD, THE USER IS ALLOWED TO LOGIN.
VALIDATE IF THE USER DOES NOT LOG OFF NORMALLY, HE IS ALLOWED RE-LOGIN.
VALIDATE IF ONLY THE USER NAME IS ENTERED RIGHT AND THE PASSWORD IS ENTERED WRONG.
VALIDATE IF ONLY THE PASSWORD IS ENTERED RIGHT AND THE USER NAME IS ENTERED WRONG.
VALIDATE IF PASSWORD IS CASE SENSITIVE.
VALIDATE IF USERNAME IS CASE SENSITIVE.
FUNCTIONALITY
VALIDATE IF THE BUSINESS REQUIREMENTS ARE BEING MET

VALIDATE FOR ACCURACY OF THE CALCULATED FIELD. ALSO WHILE VALIDATING FOR PAGE TOTAL VALIDATE ACROSS PAGES.
VALIDATE FOR USAGE OF DATA ACROSS MODULES. ADDRESS BOOK ENTRIES CAN USED IN EMAIL AND APPOINTMENTS MODULE
VALIDATE FOR APPROPRIATENESS OF FIELD SIZE FOR STORING THE DATA, I.E. FIELD SIZE OF 12 IS NOT APPROPRIATE FOR STORING NAME
LIKE 'BALASUBRAMANIAM'
VALIDATE FOR COMPLIANCE WITH THE DESIGN DOCUMENTS AND SPECIFIC PROJECT RELATED LEGAL ISSUES AND STANDARDS
VALIDATE FOR UNAUTHORIZED ACCESS OF THE SYSTEM. BOTH WITH PASSWORD SECURITY AND ACCESS LEVEL SECURITY
IF ANY FIELD HAS MULTIPLE VALIDATION RULE, VALIDATE FOR VALIDITY OF EACH OF THEM
VALIDATE FOR INCLUSION OF ZERO'S IN COMPLEX CALCULATIONS
VALIDATE FOR HANDLING OF SPECIAL CHARACTERS LIKE SINGLE QUOTES IN SEARCH OPERATIONS
VALIDATE FOR APPLICATION ACCESS WHEN THE DATABASE SERVER IS DOWN
VALIDATE FOR DIV BY 0, CAN TEST FORCE THIS CONDITION
VALIDATE FOR STORING OF PASSWORD IN ENCRYPTED FORMAT
VALIDATE FOR VALIDITY OF PASSWORD EXPIRY RULE
FORM LEVEL TEST CASES
IS THE SPELLING AND GRAMMAR CORRECT?
ARE THE NON UPDATEABLE FIELDS HAVING A GRAY BACKGROUND ?
IS THE GENERAL SCREEN BACKGROUND THE CORRECT COLOR?
ARE THE FIELD PROMPTS THE CORRECT COLOR?
ARE THE FIELD BACKGROUNDS THE CORRECT COLOR?
ARE ALL THE FIELD PROMPTS SPELT CORRECTLY?
IN READ-ONLY MODE, ARE THE FIELD PROMPTS THE CORRECT COLOR?
IN READ-ONLY MODE, ARE THE FIELD BACKGROUNDS THE CORRECT COLOR?
ARE ALL THE SCREEN PROMPTS SPECIFIED IN THE CORRECT SCREEN FONT?
IS THE TEXT IN ALL FIELDS SPECIFIED IN THE CORRECT SCREEN FONT?
ARE ALL THE FIELD PROMPTS ALIGNED PERFECTLY ON THE SCREEN?
ARE ALL THE FIELD EDIT BOXES ALIGNED PERFECTLY ON THE SCREEN?
ARE ALL GROUP BOXES ALIGNED CORRECTLY ON THE SCREEN?
IS THE SCREEN RESIZABLE?
IS THE SCREEN MINIMIZABLE?
ARE ALL THE ERROR MESSAGES SPELT CORRECTLY ON THE SCREEN?
ARE THE DIALOG BOXES HAVING A CONSISTENT LOOK AND FEEL.

VALIDATE FOR SUBMISSION OF BLANK FORM

VALIDATE FOR CANCELLATION OF BLANK FORM
VALIDATE FOR USER FORM COMPATIBILITY ON DIFFERENT SCREEN RESOLUTIONS
VALIDATE FOR DATA LOSS WHEN THE SCREEN IS MINIMIZED BEFORE SAVING THE RECORD
VALIDATE FOR DATA LOSS WHEN THE USER SWITCHES FOCUS BETWEEN APPLICATIONS BEFORE SAVING THE RECORD
VALIDATE WHETHER ALL MANDATORY FIELDS ARE HIGHLIGHTED
VALIDATE WHETHER RECORD IS ALLOWED TO BE SAVED IF DATA IS ENTERED ONLY IN THE OPTIONAL FIELDS.
VALIDATE FOR EACH MANDATORY FIELD, IF IT IS LEFT BLANK AND RECORD IS SAVED.
VALIDATE FOR UNIQUENESS IN UNIQUE FIELDS DURING ADD.
VALIDATE FOR UNIQUENESS IN UNIQUE FIELDS DURING UPDATE.
VALIDATE IF RECORD IS ALLOWED TO BE SAVED WITH MAX DATA IN ALL FIELDS
VALIDATE FOR DATA RETENTION WHEN THE BROWSER BACK AND FORWARD KEYS ARE PRESSED
RE SUBMISSION OF USER FORM AFTER DELETING DATA FROM ALL THE MANDATORY FIELDS IN UPDATE MODE.
RE SUBMISSION OF USER FORM AFTER DELETING DATA FROM ALL THE OPTIONAL FIELDS IN UPDATE MODE.
VALIDATE FOR SAVING OF DATA IN THE UPDATE MODE.
VALIDATE IF NO OF RECORDS IS DISPLAYED ACROSS THE SYSTEM ON A SINGLE PAGE BASED ON THE REQUIREMENTS.
VALIDATE IF THE ERROR MESSAGES DISPLAYED TO THE USER IN CASE OF ERROR, USES THE SAME FONT THAT IS USED ACROSS THE SYSTEM
VALIDATE IF ABBREVIATIONS USED IN CASE OF INTERNAL CODIFICATION IS NOT DISPLAYED AS A CODE TO THE USER BUT AS FULL
DESCRIPTION OF THE CODE. (E.G. DESCRIPTION 'CREDIT CARD' INTERNAL CODE 'C')
VALIDATE IF STATUS OF AN ENTITY IN THE SYSTEM IS DISPLAYED, THE SAME IS DISPLAYED AS DISABLED/ENABLED OR TRUE/FALSE OR ANY
OTHER RELEVANT STATUS AS PER THE STANDARD OF THE SYSTEM.
USABILITY
VERTICAL SCROLL DOES NOT GO BEYOND TWO PAGES.

PREFERABLY, THERE SHOULD BE NO HORIZONTAL SCROLLING.

PAGE SIZE SHOULD NOT EXCEED 65KB.IN EXCEPTIONAL CASES IT CAN GET TO 100K.REDUCING PAGE SIZE GIVES BETTER PERFORMANCE ON
THE WEB.
TRANSACTIONAL BUTTONS SHOULD BE PLACED AT THE BOTTOM OF THE SCREEN ALSO IF THE SCREEN HAS VERTICAL SCROLL BAR.
(DEPENDS ON BUSINESS REQUIREMENT THOUGH)
THERE SHOULD BE GAP BETWEEN THE LABEL AND CONTROLS. (SINGLE  )
THERE SHOULD BE GAP BETWEEN CONTROL AND CALENDAR. (SINGLE  )
CALENDAR IMAGE SHOULD BE MIDDLE ALIGNED TO THE CONTROL.
MAX. LENGTH OF THE CONTROLS SHOULD MATCH WITH THE DATABASE FIELD LENGTH.
VALIDATE FOR DISPLAY OF SYSTEM STATUS, IF BUSY THEN THE HOUR GLASS SHOULD BE DISPLAYED
VALIDATE FOR MATCHING OF THE ICONS USED WITH REAL WORLD USAGE OF THAT ICON
VALIDATE FOR CONSISTENCY ACROSS THE MODULE
VALIDATE FOR THE DISPLAY OF CHARACTERS AS LEFT ALIGNED AND NUMERIC FIELD RIGHT ALIGNED
VALIDATE FOR ACCESSIBILITY OF THE SCREEN FROM ALL THE OPTIONS PROVIDED I.E. MENUS, TOOLBAR
VALIDATE FOR THE CONTROL GOING BACK TO THE ERROR FIELD AFTER THE DISPLAY OF ERROR MESSAGE
VALIDATE FOR TOOL TIPS ON COMMAND BUTTONS
VALIDATE FOR USER BEING IN CONTROL OF THE OPERATIONS BEING PERFORMED
DOES THE TAB ORDER SPECIFIED ON THE SCREEN GO IN SEQUENCE FROM TOP LEFT TO BOTTOM RIGHT? THIS IS THE DEFAULT UNLESS
OTHERWISE SPECIFIED.
ARE ALL READ-ONLY FIELDS AVOIDED IN THE TAB SEQUENCE?
ARE ALL DISABLED FIELDS AVOIDED IN THE TAB SEQUENCE?
IS THE CURSOR POSITIONED IN THE FIRST INPUT FIELD OR CONTROL WHEN THE SCREEN IS OPENED?
WHEN AN ERROR MESSAGE OCCURS DOES THE FOCUS RETURN TO THE FIELD IN ERROR WHEN THE USER CANCELS IT?
DOES THE SCREEN HAVE A CANCEL OPERATION FOR THE USER TO CANCEL THE TRANSACTION
IS THE SCREEN MODAL. i.e. IS THE USER PREVENTED FROM ACCESSING OTHER FUNCTIONS WHEN THIS SCREEN IS ACTIVE AND IS THIS
CORRECT?
CAN A NUMBER OF INSTANCES OF THIS SCREEN BE OPENED AT THE SAME TIME AND IS THIS CORRECT?
CLICK A LINK BEFORE A PAGE IS DOWNLOADED COMPLETELY.
VERIFY WHETHER A PAGE IS DISPLAYED PROPERLY UPON CLICKING A LINK FOR CERTAIN NUMBER OF TIMES CONTINOUSLY.
VERIFY WHETHER LOGGING AND VERSION CHECKING IS HAPPENED FOR NON-WEB BASED UI.
VERIFY WHETHER ALL UIS ADHERE TO CORPORATE SECURITY SITE GUIDELINES. THE GUIDELINES CAN BE FOUND AT
http://itweb/polices/app_dev_host.htm.
VERIFY WHETHER USER FRIENDLY ERROR MESSAGE IS DISPLAYED.
DATABASE
IMPORTING DATA FROM A FILE
VERIFY BY PASSING MORE NUMBER OF COLUMNS THEN SPECIFIED.
VERIFY BY NOT PASSING THE MANDATORY FIELDS.
VERIFY BY PASSING MORE NUMBER OF CHARACTERS THEN SPECIFIED IN THE DESTINATION DATABASE FOR A PARTICULAR COLUMN.
VALIDATE DATA FOR LEADING AND TRAILING SPACES FOR THE ALPHANUMERIC COLUMNS.
VERIFY DATA BY PASSING CHARACTERS FOR A COLUMN OF DATATYPE INTEGER. ALSO VERIFY BY PASSING VALUES MORE THEN 2,147,483,647
VALIDATE FOR DIFFERENT DATE FORMATS ALONG WITH TIME
VALIDATE FOR THE FILE FORMATS
VALIDATE FOR DIFFERENT DELIMITERS.
IMPORTING DATA FROM A DATABASE
VERIFY WHETHER SOURCE AND DESTINATION COLUMNS HAVE SAME COLUMN SIZE AND DATATYPE.
VERIFY WHETHER DESTINATION TABLE IS EXISTING WITH THE SPECIFIED COLUMNS.
VERIFY WHEN A JOB IS STOPPED WHILE IT IS EXECUTING WHETHER IT IS ROLLED BACK OR IT IS STARTING FROM THAT POINT.
VALIDATE DATA AGAINST THE RULES SPECIFIED FOR EACH COLUMN/TABLE
VERIFY WHETHER PROPER ERROR MESSAGE IS DISPLAYED WHEN DATABASE SERVER (DESTINATION SERVER) GOES DOWN WHEN SOURCE
DATABASE SERVER IS HAVING ACTIVE CONNECTION.
XML INPUT PARAMETERS VALIDATION
VERIFY PASSING PARAMETERS WITH LEADING AND TRAILING SPACES.
VERIFY PASSING EMPTY PARAMETERS.

VERIFY PASSING PARAMETERS OF DIFFERENT DATATYPES. FOR EX: PASS PARAMETERS OF DATATYPE STRING FOR DATATYPE OF INTEGER

PERFORMANCE
VALIDATE FOR THE RESPONSE TIME BY SCALING UP THE SIMULTANEOUS USER ACCESS AS SPECIFIED IN BENCH MARKS.
VALIDATE FOR THE RESPONSE TIME BY SCALING UP THE DATABASE RECORDS, FROM 10000, 50000, 60000 RECORDS OR AS SPECIFIED IN THE
REQUIREMENTS
VALIDATE FOR RESOURCE UTILIZATION WHEN MULTIPLE USERS ACCESS THE SYSTEM
VALIDATE FOR RESOURCE UTILIZATION WHEN THE SYSTEM HAS BEEN OPERATIONAL FOR MULTIPLE DAYS
SECURITY
PLEASE FOLLOW THE GUIDELINES IN THE ATTACHED PRESENTATION

Presentation

INSTALLATION TESTING
VALIDATE FOR FUNCTIONING OF THE SYSTEM WITH DIFFERENT OPERATING SYSTEM AS STATED IN THE REQUIREMENT DOCUMENT
VALIDATE FOR INSTALLATION ON A CLEAN MACHINE
VALIDATE FOR PROMPTING, IN CASE OF INSUFFICIENT SPACE FOR INSTALLATION
VALIDATE THAT UNINSTALL OPERATION REMOVES ALL TRACES OF THE PROGRAM
VALIDATE FOR CANCELLATION OF INSTALLATION OPERATION MIDWAY. RE-INSTALL THE INSTALLATION PROCESS SHOULD COMPLETE
SMOOTHLY
VALIDATE FOR INSTALLATION IN THE DEFAULT DIRECTORY
VALIDATE FOR INSTALLATION IN THE USER DEFINED DIRECTORY AND WORKING OF ALL MAIN OPERATION
VALIDATE FOR INSTALLATION WITH LOGIN FILE PATH, PATH'S WITH SPACES
VALIDATE FOR MIGRATION OF DATA FROM THE OLD SYSTEM
VALIDATE FOR INSTALLATION OF APPLICATION ON ONE MACHINE AND DATABASE ON ANOTHER MACHINE
VALIDATE FOR PRINTING ON DIFFERENT TYPE OF PRINTERS
VERIFY WHETHER ALL THE TABLES/VIEWS HAS BEEN CREATED WELL BEFORE AS SPECIFIED IN THE FUNCTIONAL SPEC'S
VERIFY WHETHER ALL THE CONSTRAINTS AND INDEXES HAS BEEN CREATED AS SPECIFIED IN THE FUNCTIONAL SPEC'S
VERIFY WHETHER THE BUILD PROCESS ABLE TO RESTART FROM THE FAILURE MODE.
VERIFY WHETHER THE LONG BUILD PROCESS ARE MONITORED AND LOGGED EXACTLY.
DATABASE TESTING
PLEASE FOLLOW THE GUIDELINES IN THE ATTACHED PRESENTATION

ACCESSIBILITY TESTING
GENERAL TEST CASES
VALIDATE WHETHER SOFTWARE PROVIDE KEYBOARD EQUIVALENTS FOR ALL MOUSE ACTIONS, INCLUDING BUTTONS, SCROLL WINDOWS,
TEXT ENTRY FIELDS, AND POP-UP WINDOWS

VALIDATE WHETHER PROGRAM PROVIDE CLEAR AND PRECISE INSTRUCTIONS FOR USE OF ALL KEYBOARD FUNCTIONS AS PART OF THE USER
DOCUMENTATION
VALIDATE INSTRUCTIONS REGARDING KEYBOARD USE WIDELY AVAILABLE FOR ALL USERS IN YOUR COMPONENT
VALIDATE WHETHER SOFTWARE HAVE A LOGICAL TABBING ORDER AMONG FIELDS, TEXT BOXES, AND FOCAL POINTS
VALIDATE DOES THE FOCUS FOLLOW A LOGICAL TABBING ORDER NAVIGATING SCREENS AND DIALOG BOXES USING THE KEYBOARD
VALIDATE IF THERE IS A WELL-DEFINED FOCAL POINT THAT MOVES WITH KEYBOARD NAVIGATION? (E.G., CAN YOU USE THE ARROW KEYS TO
NAVIGATE THROUGH A LIST FOLLOWED BY PRESSING THE ENTER KEY OR SPACE BAR TO SELECT THE DESIRED ITEM)

VALIDATE WHETHER SHORTCUT KEYS PROVIDED FOR ALL PULL-DOWN MENUS

VALIDATE FOR SOFTWARE SUPPORT FOR EXISTING ACCESSIBILITY FEATURES BUILT INTO THE OPERATING SYSTEM (E.G., STICKY KEYS, SLOW
KEYS, REPEAT KEYS IN APPLE MACINTOSH OS OR MICROSOFT WINDOWS 95)?

IF TIMED RESPONSES ARE PRESENT, DOES THE SOFTWARE ALLOW THE USER TO MODIFY THE TIMING PARAMETERS OF ANY REQUIRED TIMED
RESPONSES?

VALIDATE ALL DESCRIPTIONS OR LABELS FOR FIELDS POSITIONED IMMEDIATELY TO THE LEFT OR DIRECTLY ABOVE THE CONTROL, AND DO
THEY END IN A COLON, SO THAT IT IS EASY FOR SCREEN READING SOFTWARE TO ASSOCIATE THE LABELS WITH THE CORRESPONDING FIELD
VALIDATE WHETHER EVERY WINDOW, OBJECT, AND CONTROL HAVE A CLEARLY NAMED LABEL
VALIDATE THE SOFTWARE APPLICATION USE STANDARD CONTROLS RATHER THAN OWNER-DRAWN OR CUSTOM CONTROLS
DOES THE SOFTWARE HAVE A USER SELECTABLE OPTION TO DISPLAY TEXT ON ICONS, I.E., TEXT ONLY ICONS OR BUBBLE HELP?
VALIDATE WHETHER THE USE OF ICONS CONSISTENT THROUGHOUT THE APPLICATION
VALIDATE WHETHER MENUS WITH TEXT EQUIVALENTS PROVIDED FOR ALL ICON FUNCTIONS OR ICON SELECTIONS ON MENU, TOOL, AND
FORMAT BARS
IF THERE ARE AUDIO ALERTS, ARE VISUAL CUES ALSO PROVIDED
NOTE: MOST OPERATING SYSTEMS HANDLE THIS ISSUE IN THE
CLIENT/SERVER ENVIRONMENT; THE QUESTION IS MOST RELEVANT IN A DUMB TERMINAL ENVIRONMENT
VALIDATE WHETHER THE SOFTWARE SUPPORT THE "SHOW SOUNDS" FEATURE WHERE IT IS BUILT INTO THE OPERATING SYSTEM
VALIDATE WHETHER USER DISABLE OR ADJUST SOUND VOLUME
IF INFORMATION IS PROVIDED IN AN AUDIO FORMAT, IS IT ALSO CAPABLE OF BEING DISPLAYED BY THE USER IN A VISUAL FORMAT?
IS THE SOFTWARE APPLICATION FREE OF PATTERNED BACKGROUNDS USED BEHIND TEXT OR IMPORTANT GRAPHICS?
VALIDATE WHETHER A USER CAN OVERRIDE DEFAULT FONTS FOR PRINTING AND TEXT DISPLAYS?
VALIDATE WHETHER A USER CAN ADJUST OR DISABLE FLASHING, ROTATING, OR MOVING DISPLAYS
VALIDATE THE SOFTWARE TO ENSURE THAT COLOR-CODING IS NEVER USED AS THE ONLY MEANS OF CONVEYING INFORMATION OR
INDICATING AN ACTION
VALIDATE THE APPLICATION SUPPORTS USER-DEFINED COLOR SETTINGS SYSTEM-WIDE
IS HIGHLIGHTING ALSO VIEWABLE WITH INVERTED COLORS?
IF THE SOFTWARE APPLICATION DRAWS ITS OWN SCREEN ELEMENTS, DOES IT PICK UP THE SIZE SETTINGS THAT THE USER HAS SELECTED
THE CONTROL PANEL?
VALIDATE ALL MANUALS AND DOCUMENTATION PROVIDED IN ELECTRONIC FORMAT AS WELL AS ASCII TEXT FILES, INCLUDING TEXT
DESCRIPTIONS OF ANY CHARTS, GRAPHS, PICTURES, OR GRAPHICS OF ANY NATURE?

VALIDATE WHETHER A USER CAN CHOOSE TO HAVE ANY REPORT GENERATED BY THE SOFTWARE MADE AVAILABLE IN A "PRINT TO ASCII FILE"
FORMAT?
IS SPECIAL TRAINING PROVIDED FOR USERS WITH DISABILITIES THAT WILL ENABLE THEM TO BECOME FAMILIAR WITH THE SOFTWARE AND
LEARN HOW TO USE IT IN CONJUNCTION WITH ASSISTIVE TECHNOLOGY PROVIDED AS AN ACCOMMODATION?
WEB ACCESSIBILITY TEST CASES
VALIDATE ALL PAGES ON THE SITE HAVE A HIGHLY CONSISTENT STYLE WITH PREDICTABLE LAYOUT OF ELEMENTS.
VALIDATE FULL AND EQUIVALENT ALTERNATIVE DESCRIPTIONS ARE PROVIDED FOR ALL IMAGES
VALIDATE SEPARATE, REDUNDANT, DESCRIPTIVE TEXT LINKS ARE PROVIDED FOR ALL IMAGE LINKS AND IMAGE MAPS.
VALIDATE ALTERNATIVE METHODS TO FORMS ARE INCLUDED AND SUPPORTED IN ORDER TO COLLECT INFORMATION FROM USERS.

VALIDATE FRAMES ARE NOT USED OR IF THEY ARE A CLEAR ALTERNATIVE METHOD IS USED TO PROVIDE EQUIVALENT INFORMATION TO THAT
IN THE FRAMED VERSION.
VALIDATE TABLES ARE USED ONLY FOR DATA DISPLAY OR SPARINGLY FOR FORMATTING PAGES. ALL TABLES DEGRADE GRACEFULLY.
VALIDATE ALL VIDEO CLIPS, AUDIO CLIPS ETC. HAVE EQUIVALENT CONTENT PROVIDED SUCH AS DESCRIPTIONS AND SUBTITLES.

VALIDATE BACKGROUND IMAGES AND BACKGROUND COLOURS ARE NOT USED, OR USED CAREFULLY TO AVOID REDUCING CLARITY THROUG
LACK OF CONTRAST.

VALIDATE ALL PAGES ALLOW THE DEFAULT SIZE OF THE TEXT TO BE ALTERED BY THE USERS. WHEN REFORMATTED IN DIFFERENT SIZES THE
PAGE REMAINS CLEAR AND UNDERSTANDABLE.
VALIDATE ALL SENTENCES, PARAGRAPHS, HEADERS AND TITLES CONTAIN AND END IN APPROPRIATE PUNCTUATION MARKS.
VALIDATE ALL PAGES ARE STRUCTURED USING APPROPRIATE HTML TAGS. TAGS ARE NOT MISUSED TO PROVIDE STYLISTIC EFFECTS.
VALIDATE STYLE SHEETS ARE IMPLEMENTED CORRECTLY. IN-LINE <FONT> DEFINITIONS ARE AVOIDED.
VALIDATE BLINKING AND SCROLLING ELEMENTS ARE AVOIDED.
VALIDATE ALL PAGES WORK USING DIFFERENT SCREEN RESOLUTIONS, WINDOW SIZES AND ON DIFFERENT DEVICES AND WITH DIFFERENT
BROWSER SOFTWARE.

VALIDATE LINKS ARE DESCRIPTIVE AND PREDICTIVE OF THEIR LINK DESTINATION EVEN WHEN VIEWED IN ISOLATION. NO USE OF 'CLICK HERE
ETC.
VALIDATE ALL ACRONYMS AND ABBREVIATIONS ARE MARKED AND EXPANDED USING THE <ABBR> AND <ACRONYM> TAGS.
VALIDATE THE BASE LANGUAGE OF EACH PAGE OR SECTION IS SPECIFIED.
VALIDATE ALL PAGES INCLUDE A DOCUMENT TYPE DECLARATION (E.G. THE STRICT HTML 4.0 DTD).
VALIDATE ALL PAGES MAKE SENSE AND ARE USABLE WITH IMAGES AND CASCADING STYLE SHEETS TURNED OFF.