Professional Documents
Culture Documents
VERSION HISTORY VERSION Draft 0.1 Issue 1.0 VER. DATE 11/13/2001 2/15/2002
klist
: PREPARED BY Sreela Sreela REASON FOR CHANGE Draft Issue after the review
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
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
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
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