You are on page 1of 8

Testing Checklist DOCUMENT NAME: ABSTRACT: DOCUMENT REFERENCE: AUTHORISATION: TestingChecklist This document should be refered while creating

the Test Plan and Test Cases Testing Process Document

Prepared By Name : Sreela Chandran Signature :

Reviewed By Name :Naina Shetty Signature : Name :Ninad Kulkarni Signature :

DISTRIBUTION LIST COPY NO MASTER ISSUED TO LAN : \mobi-assist\Quality\Training

VERSION HISTORY VERSION Draft 0.1 Issue 1.0 VER. DATE 11/13/2001 2/15/2002

klist

g the Test Plan and Test Cases

Authorised By Name :Sreela Chandran Signature :

: PREPARED BY Sreela Sreela REASON FOR CHANGE Draft Issue after the review

Guidelines for phasewise Defect sub classification


Test Plan has unique identifier - name as per the state project format Approval Name should be stated Document Control section and the Page footer is in sink The Introduction & scope has been clearly stated Aims of the integration testing should be mentioned clearly. Test Objective should be clearly stated Reference to Related document has been stated and they are appropriate. I.e RDD, Project Plan etc. Ther version number of these document is appropriate. Items that would be tested has been stated with their version number, I.e. VersaViews 1.2, On-line Help 1.2 Items which are specifically not going to be tested have been stated(optional) Features that would be tested has been clearely stated Features that would not be tested has been clearely stated, along with the reasons. Overall approach to testing has been stated Management of testing process should be mentioned in the test plan. Test progress and reporting process should be mentioned in the test plan Problem reporting process should be mentioned The approach for review of the test cases should be mentioned. The Tools being used has been stated The rquirment traceability has been stated The Entry and Exit criteria has been stated Test suspension/resumption criteria has been stated Roles and responsibilities should be stated clearly. Test Deliverables has been stated Test Schedule is appropriate. It takes care of each testing activity I.e. Sanity Test, Installation Test, Functional Test, Performance Test, Security Test etc. Time for Test Plan and Case creation is allocated. Also, time for Reviews, status reporting and defect prioritization should be allocated. Test Environment need has been specified.H/W & Software Responsibilities of all the cross functional team should be stated Identify Risk. Contigency Plan has also been stated. Test team organisation should be stated in the test plan

3 of 8

Technical terms and and abbreviation should be mentioned in the test cases document. Objectives and scope should be mentioned in the test cases document Test Case description is appropriate for the test being carried out Features to be tested should be mentioned in the test case document Only appropriate steps required for executing the tests has been stated Test Cases design is repeatable. It is person independent. Test data is stated clearly. Any tester can execute the same and the end result would be the same. Test case is traceable to a requirement. The Requirement no. is stated correctly against the test case. Test case numbering format is being followed correctly Failure impact, failure probability and environmental impact should be mentioned for each test case. Input screens used, instructions to carry on testing , expected data , expected output should be mentioned for each test case. Pre-requisite data if required is stated. Data w.r.t Referential Integrity, Security level access etc. Actions and steps are clearly stated There is no ambiguity in the expected results Special requirements should be mentioned clearly for the test case. If any Log or Report need to be saved. It is stated appropriately. Test logs should be mentioned for testing of each version of new release. The action does not exceed 10 steps The test cases are ordered as per the business scenario. All related test cases are grouped together. Test case document should have a appropriate Document Control Page The version numbers are updated appropriately. Both in the Document control section and Page Footer

Form Level Checks


CHECK FOR SUBMISSION OF BLANK FORM CHECK FOR CANCELLATION OF BLANK FORM CHECK FOR USER FORM COMPATIBILITY ON DIFFERENT SCREEN RESOLUTIONS CHECK FOR DATA LOSS WHEN THE SCREEN IS MINIMIZED BEFORE SAVING THE RECORD CHECK FOR DATA LOSS WHEN THE USER SWITCHES FOCUS BETWEEN APPLICATIONS BEFORE SAVING THE RECORD CHECK FOR THE TAB ORDER IN THE FORM WHEN DATA IS INPUT ON THE FORM CHECK WHETHER ALL MANDATORY FIELDS ARE HIGHLIGHTED CHECK WHETHER RECORD IS ALLOWED TO BE SAVED IF DATA IS ENTERED ONLY IN THE OPTIONAL FIELDS. CHECK FOR EACH MANDATORY FIELD, IF IT IS LEFT BLANK AND RECORD IS SAVED. CHECK FOR UNIQUENESS IN UNIQUE FIELDS DURIING ADD. CHECK FOR UNIQUENESS IN UNIQUE FIELDS DURIING UPDATE. CHECK IF RECORD IS ALLOWED TO BE SAVED WITH MAX DATA IN ALL FIELDS CHECK FOR DATA RETENSION 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. CHECK FOR SAVING OF DATA IN THE UPDATE MODE. CHECK IF STANDARD NO OF RECORDS IS DISPLAYED ACROSS THE SYSTEM ON A SINGLE PAGE. CHECK IF THE CONTENTS OF THE LISTBOXES IN THE SYSTEM ARE SORTED IN ASCENDING ORDER. CHECK IF THE CONTENT SORTING IN THE LISTBOXES IS NOT CASE-SENSITIVE. i.e. THE LIST SHOULD DISPLAY 'A' BEFORE 'a' AND 'a' BEFORE 'Z'. CHECK IF THE LISTBOXES HAVE 'ALL' OR 'PLEASE SELECT' OPTION AS REQUIRED. CHECK IF THE DATE DISPLAYED IS IN STANDARD FORMAT OF THE SYSTEM. FOR EG:DD/MM/YYYY CHECK IF THE FORM DISPLAYED USES THE SAME FONT THAT IS USED ACROSS THE SYSTEM CHECK IF THE ERROR MESSAGES DISPLAYED TO THE USER IN CASE OF ERROR, USES THE SAME FONT THAT IS USED ACROSS THE SYSTEM CHECK IF ABBREVIATIONS USED IN CASE OF INTERNAL CODIFICATION IS NOT DISPLAYED AS A CODE TO THE USER BUT AS FULL DESCRIPTION OF THE CODE. (er. Description 'CREDIT CARD' internal code 'C') CHECK 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.

Field Level Checks


CHECK IF LEADING SPACES ARE ENTERED IN A ALPHANUMERIC FIELD, THE SAME IS TRIMMED BEFORE SAVING THE RECORD. CHECK IF TRAILING SPACES ARE ENTERED IN A ALPHANUMERIC FIELD, THE SAME IS TRIMMED BEFORE SAVING THE RECORD. CHECK IF ONLY SPACES ARE ENTERED THE SAME IS NOT ALLOWED TO BE SAVED CHECK IF ANY PRIMARY KEY FIELD THAT IS GOING TO BE DISPLAYED IS NOT CASE SENSITIVE CHECK IF FIELD LENGTH IS 20 AND DATA ENTERED IS 12 SPACES + 12 CHARACTERS. THE RECORD IS NOT SAVED. CHECK FOR BOUNDARY CONDITIONS IN NUMERIC FIELDS. CHECK FOR ALPHANUMERIC DATA IN NUMERIC FIELDS. CHECK IF NEGATIVE NUMBERS IS NOT ACCEPTABLE IN NUMERIC FIELDS WHICH SHOULD EXPECT POSITIVE NUMBERS.

CHECK IF ANY VALUE IS BEING DISPLAYED FOR NUMERIC DATA, THE SAME IS DISPLAYED ALONG WITH TWO DECIMAL PLACES UNLESS IT IS SYSTEM SPECIFIC. FOR EG: Rs. 147 SHOULD BE DISPLAYED AS Rs. 147.00

Password field Checks


CHECK IF THE PASSWORD FIELD IS LEFT BLANK AND RECORD IS SAVED CHECK IF THE RE- ENTER PASSWORD FIELD IS LEFT BLANK AND RECORD IS SAVED. CHECK FOR ACCEPTANCE OF LEADING SPACES IN THE PASSWORD FIELD, THE SAME ARE SAVED. CHECK FOR ACCEPTANCE OF TRAILING SPACES IN THE PASSWORD FIELD, THE ARE SAVED. CHECK IF ONLY SPACES ARE ALLOWED TO BE SAVED IN THE PASSWORD FIELD CHECK IF ONLY QUOTES ARE ALLOWED TO BE SAVED IN THE PASSWORD FIELD CHECK WHETHER LEADING SPACES IN THE RE- ENTER PASSWORD FIELD ARE SAVED. CHECK WHETHER TRAILING SPACES IN THE RE-ENTER PASSWORD FIELD ARE SAVED. CHECK IF ONLY SPACES ARE ALLOWED TO BE SAVED IN THE RE-ENTER PASSWORD FIELD CHECK IF ONLY QUOTES ARE ALLOWED TO BE SAVED IN THE RE-ENTER PASSWORD FIELD CHECK IF RE-ENTER PASSWORD AND PASSWORD FIELDS CONTAIN DIFFERENT DATA CHECK 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 Checks.


CHECK IF ATLEAST ONE @ AND '.' ARE PRESENT IN EMAIL ID FIELD CHECK IF SPACES TRIMMED IN THE BEGINNING AND END OF EMAIL ID FIELD CHECK IF ONLY SPACES ALONG WITH @ AND . IS NOT ALLOWED TO BE SAVED IN EMAIL ID FIELD CHECK IF EMAIL ID FIELD IS UNIQUE FOR A RECORD DEPENDING ON THE USABILITY. CHECK IF EMAIL ID FIELD IS CASE INSENSITIVE CHECK IF EMAIL ID FIELD ACCEPTS QUOTES

Parameter Screen & Reports Checks


CHECK FOR BLANK INPUTS IN THE FROM RANGE FIELD IS ACCEPTABLE. CHECK FOR BLANK INPUTS IN BOTH FROM RANGE FIELD AND TO RANGE FIELD IS ACCEPTABLE CHECK FOR BLANK INPUTS IN TO RANGE FIELD IS ACCEPTABLE. CHECK IF VALUE IN TO RANGE FIELD IS SMALLER THAN FROM FIELD IS NOT ACCEPTABLE. CHECK 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 OG THE QUERY. CHECK IF BLANK SCREEN IS SUBMITTED THEN ALL THE RECORDS ARE DISPLAYED. CHECK IF THE RESULT PAGE DISPLAYS THE NO. OF RECORDS FOUND FOR THE QUERY. CHECK IF THE RESULT PAGE DISPLAYS NEW QUERY LINK TO GO BACK TO THE QUERY PAGE CHECK IF STANDARD NO. OF RECORDS IS DISPLAYED ON A SINGLE RESULT PAGE OF THE REPORT. CHECK IF THE BUTTON ON THE PARAMETER SCREEN IS LABLED AS 'SEARCH'. CHECK IF NEXT AND PREVIOUS BUTTONS ARE PRESENT ON A PAGE, THE SAME IS LABELED AS 'NEXT' AND 'PREV' AND IS POSITIONED ON THE RIGHT HAND SIDE AND LEFT HAND SIDE OF THE SCREEN RESPECTIVELY. CHECK IF THE ALPHANUMERIC DATA & LABELS DISPLAYED IN THE REPORT IS LEFT ALIGNED. CHECK IF THE NUMERIC DATA & LABELS DISPLAYED IN THE REPORT IS RIGHT ALIGNED. CHECK IF THE NUMERIC DATA & LABELS REPRESENTING ID FIELDS OR LINKS IS DISPLAYED AS LEFT ALIGNED.

MultiUser Checks
SUBMISSION OF A FORM FROM TWO DIFFERENT MACHINES CHECK IF THE TWO DIFFERENT USERS ACCESS THE SAME RECORD FROM DIFFERENT MACHINES. CHECK IF THE SAME USER IS ALLOWED TO ACCESS THE SAME RECORD FROM DIFFERENT MACHINES. CHECK IF IN CASE OF MULTIUSER OPERATIONS, IF ANY UNIQUE KEY OR PRIMARY KEY IS VIOLATED, APPROPRIATE ERROR MESSAGE IS SHOWN TO ONE OF THE USER. CHECK FOR THE CHANGES IN MASTER DATA, WHEN THE SAME IS BEING USED IN THE TRANSACTION FROM THE OTHER TERMINAL

Login Related Checks


CHECK FOR SUBMISSION OF BLANK LOGIN SCREEN. CHECK FOR CANCELLATION ON BLANK LOGIN SCREEN. CHECK FOR THE FOCUS ON THE FIRST TEXT FIELD IN THE LOGIN SCREEN AFTER INVOKING THE SCREEN CHECK FOR THE FOCUS ON THE LOGIN BUTTON IN THE LOGIN SCREEN AFTER INVOKING THE SCREEN CHECK FOR SIMULTANEOUS LOGGING OF DIFFERENT TYPES OF USERS WITH THE SAME USER NAME AND PASSWORD. CHECK IF THE USER NAME FIELD IS LEFT BLANK AND USER CLICKS ON LOGIN CHECK IF THE PASSWORD FIELD IS LEFT BLANK AND USER CLICKS ON LOGIN. CHECK IF AFTER CHANGING THE PASSWORD AND SAVING THE RECORD, THE USER IS ALLOWED TO LOGIN. CHECK IF THE USER DOES NOT LOG OFF NORMALLY, HE IS ALLOWED RE-LOGIN. CHECK IF ONLY THE USER NAME IS ENTERED RIGHT AND THE PASSWORD IS ENTERED WRONG. CHECK IF ONLY THE PASSWORD IS ENTERED RIGHT AND THE USER NAME IS ENTERED WRONG. CHECK IF PASSWORD IS CASE SENSITIVE. CHECK IF USERNAME IS CASE SENSITIVE.

FUNCTIONALITY
CHECK IF THE BUSINESS REQUIREMENTS ARE BEING MET CHECK FOR ACCURACY OF THE CALCULATED FIELD. ALSO WHILE CHECKING FOR PAGE TOTAL CHECK ACROSS PAGES. CHECK FOR USAGE OF DATA ACROSS MODULES. ADDRESS BOOK ENTRIES CAN USED IN EMAIL AND APPOINTMENTS MODULE CHECK FOR APPROPRIATENESS OF FIELD SIZE FOR STORING THE DATA, I.E. FIELD SIZE OF 12 IS NOT APPROPRIATE FOR STORING NAME LIKE 'BALASUBRAMANIAM' CHECK FOR COMPLIANCE WITH THE DESIGN DOCUMENTS AND SPESIFIC PROJECT RELATED LEGAL ISSUES AND STANDARDS CHECK FOR UNAUTHORISED ACCES OF THE SYSTEM. BOTH WITH PASSWORD SEURITY AND ACCESS LEVEL SECURITY IF ANY FIELD HAS MULTIPLE VALIDATION RULE, CHECK FOR VALIDITY OF EACH OF THEM CHECK FOR INCLUSION OF ZERO'S IN COMPLEX CALCULATIONS CHECK FOR HANDLING OF SPECIAL CHARACTERS LIKE SINGLE QUOTES IN SEARCH OPERATIONS CHECK FOR APPLICATION ACCESS WHEN THE DATABASE SERVER IS DOWN CHECK FOR DIV BY 0, CAN TEST FORCE THIS CONDITION CHECK FOR STORING OF PASSWORD IN ENCRYPTED FORMAT CHECK FOR VALIDITY OF PASSWORD EXPIRY RULE

USABILITY
CHECK FOR DISPLAY OF SYSTEM STATUS, IF BUSY THEN THE HOUR GALSS SHOULD BE DISPLAYED CHECK FOR MACHING OF THE ICONS USED WITH REAL WORLD USAGE OF THAT ICON CHECK FOR CONSISTENCY ACROSS THE MODULE CHECK FOR EASY UNDERSTANDABILITY OF THE SYSTEM CHECK FOR DISPLAY OF CURSOR IN THE FIRST FIELD CHECK FOR THE DISPLAY OF CHARACTERS AS LEFT ALIGNED AND NUMERIC FIELD RIGHT ALIGNED CHECK FOR ACCESSIBILITY OF THE SCREEN FROM ALL THE OPTIONS PROVIDED I.E. MENUS, TOOLBAR CHECK FOR THE TAB ORDER CHECK FOR THE CONTROL GOING BACK TO THE ERROR FIELD AFTER THE DISPLAY OF ERROR MESSAGE CHECK FOR TOOL TIPS ON COMMAND BUTTONS CHECK FOR USER BEING IN CONTROL OF THE OPERATIONS BEING PERFORMED

PORTABILITY
CHECK FOR FUNCTIONING OF THE SYSTEM WITH DIFFERENT OPERATING SYSTEM AS STATED IN THE REQUIREMETNT DOCUMENT CHECK FOR INSTALLATION ON A CLEAN MACHINE CHECK FOR PROPMTING, IN CASE OF INSUFFICIENT SPACE FOR INSTALLATION CHECK THAT UNINSTALL OPERATION REMOVES ALL TRACES OF THE PROGRAM CHECK FOR CANCELLATION OF INSTALLATION OPERATION MIDWAY. RE-INSTALL THE INSTALLATION PROCESS SHOULD COMPLETE SMOOTHLY CHECK FOR INSTALLATION IN THE DEFAULT DIRECTORY CHECK FOR INSTALLATION IN THE USER DEFINED DIRECTORY AND WORKING OF ALL MAIN OPERATION CHECK FOR INSTALLATION WITH LOGN FILE PATH, PATH'S WITH SPACES CHECK FOR MIGRATION OF DATA FROM THE OLD SYSTEM CHECK FOR INSTALLATION OF APPLICATION ON ONE MACHINE AND DATABASE ON ANOTHER MACHINE CHECK FOR PRINTING ON DIFFERENT TYPE OF PRINTERS

RELIABILITY
CHECK FOR THE SYSTEM BEING ACCESSED FOR 24 * 7

EFFICIENCY
CHECK FOR THE RESPONSE TIME BY SCALLING UP THE SIMULTANEOUS USER ACCESS CHECK FOR THE RESPONSE TIME BY SCALLING UP THE DATABASE RECORDS, FROM 10000, 50000, 60000 RECORDS CHECK FOR RESOURCE UTILIZATION WHEN MULTIPLE USERS ACCESS THE SYSTEM CHECK FOR RESOURCE UTILIZATION WHEN THE SYSTEM HAS BEEN OPERATIONAL FOR MULTIPLE DAYS

You might also like