TC Name: Country Master Table Objective: To test the data validations of Country Master Table TC ID Test Case check

field CountryID for 1 data validation. 1 2

check field CountryID for new 3 key generation

Validation Should allow only entry to numeric data (0-9)

Should allow entry to only numeric data (0-9) Should allow only entry to numeric data (0-9) CountryID should be unique CountryID should be unique

Test Data enter A-Z

enter a-z enter special characters insert a new row in table delete an existing row and insert a new row try to delete a row having a linking row in StateMaster Table Modify an existing CountryID Should allow any alphanumeric characters except any special characters enter any name exceeding 100 chars Insert a new row in table leaving CountryName as NULL Insert a new row in table leaving CountryName as blank spaces

check for referential integrity CountryID should follow Referential integrity 5 of CountryID 6
CountryID should follow Referential integrity Should allow any alphanumeric characters except any special characters CountryName should not be more than 100 characters CountryName is mandatory and cannot be NULL CountryName is mandatory and cannot be blank

check field CountryName for 7 data validation.

8 9 10

check field CountryID for new 11 key generation

insert a new row with CountryName = 'India'. Now insert another new CountryName should be unique row with CountryName = 'India' Should allow any alphanumeric characters except any special characters Curreny should not be more than 5 characters enter any special characters other than (A-Z, a-z, 0-9, space and single quote try to delete a row having a linking row in CityMaster Table should allow any data should allow any data should allow any data try to enter any data not in date format

12 13 14 15 16

Check field Currency for data validations check for referential integrity of CountryID check field AppName for data validation check field HostName for data validations check field CreateDate for data

17 validations

check field AppName for

18 functional validation

insert a new row in table to check if this field should trac which the field automatically takes the application inserted the new row name of the application, using what or modified the existing row the row has been inserted

19

modify an existing row in table to check if the field automatically this field should trac which takes the name of the application, application inserted the new row using what the row has been or modified the existing row modified

check field HostName for

20 functional validation

insert a new row in table to check if this field should trac from which the field automatically takes the computer the new row has been name of the computer from which inserted or modified the row has been inserted

21

modify an existing row in table to check if the field automatically this field should trac from which takes the name of the computer computer the new row has been from which the row has been inserted or modified modified

check field UserName for

22 functional validation

insert a new row in table to check if this field should trac the user the field automatically takes the name who has inserted the new name of the user who inserted the row or modified an existing row new row

23

check field ModifyDate for

24 functional validation

modify an existing row in table to this field should trac the user check if the field automatically name who has inserted the new takes the name of the user who row or modified an existing row modified the existing row insert a new row in table to check if this field should trac the date on the field automatically takes the which the new row has been date on which the row has been inserted inserted Modify an existing row in table to this field should trac the date on check if the field automatically which the new row has been takes the date on which the row has inserted been Modified

25 26 27 28 29 30 31

Remarks should not accept the test data

should not accept the test data should not accept the test data should generate a new CountryID the deleted row's CountryID should not be repeated Should not allow to delete the record Should not allow to modify the record

should not accept the test data should not accept data more than 100 chars should not allow to insert a new row should not allow to insert a new row

should not accpet same country name twice

should not accept the test data should not accept data more than 5 chars should allow any data should allow any data should allow any data should not accept the test data on a new row entry, this field should automatically take the name of application using what the row has been inserted e.g. if a new row has been inserted using MySQL query browser, this field should show 'My SQL query browser'

on modifying the row, this field should automatically take the name of application using what the row has been modified e.g. if the row has been modified using c# application Vista NE-DSS, this field should show 'Vista NE-DSS' on a new row entry, this field should automatically take the name of computer from which the row has been inserted e.g. if a new row has been inserted from COMP1, this field should show 'COMP1' on modifying the row, this field should automatically take the name of computer from which the row has been modified e.g. if the row has been modified from SERVER1, this field should show 'SERVER1' on a new row entry, this field should automatically take the name of the user who inserted the new row e.g. if a new row has been inserted by User1, this field should show 'User1' on modifying the row, this field should automatically take the name of the user who has modified the row e.g. if user User2 has modified the row this field should show 'User2' on a new row entry, this field should automatically take the date on which the row has been inserted on modifying an existing row entry, this field should automatically take the date on which the row has been modified

TC NAME : STATE MASTER TABLE OBJECTIVE : TO TEST THE FUNCTIONALITY OF THE STATE MASTER TABLE

TC ID

TEST CASE
check state id field for data 1 validation

VALIDATION

TEST DATA
enter A-Z enter a-z enter special characters Should allow any alphanumeric characters except any special characters enter any name exceeding 100 chars Insert a new row in table leaving CountryName as NULL Insert a new row in table leaving CountryName as blank spaces enter A-Z enter a-z enter special characters insert a new row in table delete an existing row and insert a new row try to delete a row having a linking row in CityMaster Table Modify an existing CountryID Should allow any alphanumeric characters except any special characters enter any name exceeding 100 chars Insert a new row in table leaving CountryName as NULL Insert a new row in table leaving CountryName as blank spaces

2 3

7 8 9 10 11 12 13 14

15

16

17

18

Should allow entry to only numeric data (0-9) Should allow only entry to numeric data (0-9) Should allow only entry to numeric data (0-9) Should allow any alphanumeric characters check state name field for except any special data validation characters CountryName should not be more than 100 characters CountryName is mandatory and cannot be NULL CountryName is mandatory and cannot be blank check field CountryID for Should allow only entry to data validation. numeric data (0-9) Should allow only entry to numeric data (0-9) Should allow only entry to numeric data (0-9) check field CountryID for new CountryID should be key generation unique CountryID should be unique check for referential integrity CountryID should follow of CountryID Referential integrity CountryID should follow Referential integrity Should allow any alphanumeric characters check field CountryName for except any special data validation. characters CountryName should not be more than 100 characters CountryName is mandatory and cannot be NULL CountryName is mandatory and cannot be blank

19 unique key constraint 20 21 22 23

Check field CountryName for CountryName should be unique check field AppName for data validation check field HostName for data validations check field UserName for data validations check field CreateDate for data validations

insert a new row with CountryName = 'India'. Now insert another new row with CountryName = 'India' should allow any data should allow any data should allow any data try to enter any data not in date format

check field AppName for

24 functional validation

this field should trac which application inserted the new row or modified the existing row

insert a new row in table to check if the field automatically takes the name of the application, using what the row has been inserted but not more then 45 VARCHAR

25

this field should trac which application inserted the new row or modified the existing row

modify an existing row in table to check if the field automatically takes the name of the application, using what the row has been modified

check field HostName for

26 functional validation

this field should trac from which computer the new row has been inserted or modified

insert a new row in table to check if the field automatically takes the name of the computer from which the row has been inserted and not more then 45 VARCHAR

27

this field should trac from which computer the new row has been inserted or modified

modify an existing row in table to check if the field automatically takes the name of the computer from which the row has been modified

check field UserName for

28 functional validation

this field should trac the user name who has inserted the new row or modified an existing row

insert a new row in table to check if the field automatically takes the name of the user who inserted the new row & not more then 45 VARCHAR

29

this field should trac the user name who has inserted the new row or modified an existing row

check field ModifyDate for

30 functional validation

modify an existing row in table to check if the field automatically takes the name of the user who modified the existing row insert a new row in table to check this field should trac the if the field automatically takes the date on which the new row date on which the row has been has been inserted inserted Modify an existing row in table to this field should trac the check if the field automatically date on which the new row takes the date on which the row has been inserted has been Modified

31

EXPECTED RESULTS
should not accept the test data should not accept the test data should not accept the test data

ACTUAL RESULT

SUCCESS/FAILURE

REMARKS/SUGGES SIONS

should not accept the test data should not accept data more than 100 chars should not allow to insert a new row should not allow to insert a new row should not accept the test data should not accept the test data should not accept the test data should generate a new CountryID the deleted row's CountryID should not be repeated Should not allow to delete the record Should not allow to modify the record

should not accept the test data should not accept data more than 100 chars should not allow to insert a new row should not allow to insert a new row

should not accpet same country name twice should allow any data should allow any data should allow any data It should not be accepted on a new row entry, this field should automatically take the name of application using what the row has been inserted e.g. if a new row has been inserted using MySQL query browser, this field should show 'My SQL query browser' And it should not accept more then 45 V ARCHAR on modifying the row, this field should automatically take the name of application using what the row has been modified e.g. if the row has been modified using c# application Vista NEDSS, this field should show 'Vista NE-DSS' on a new row entry, this field should automatically take the name of computer from which the row has been inserted & it should not accept more then 45 VARCHAR e.g. if a new row has been inserted from COMP1, this field should show 'COMP1' on modifying the row, this field should automatically take the name of computer from which the row has been modified e.g. if the row has been modified from SERVER1, this field should show 'SERVER1'

on a new row entry, this field should automatically take the name of the user who inserted the new row & should not accept more then 45VARCHAR e.g. if a new row has been inserted by User1, this field should show 'User1' on modifying the row, this field should automatically take the name of the user who has modified the row e.g. if user User2 has modified the row this field should show 'User2' on a new row entry, this field should automatically take the date on which the row has been inserted on modifying an existing row entry, this field should automatically take the date on which the row has been modified

TC NAME : CITY MASTER TABLE OBJECTIVE: TO TEST THE FUNCTIONALITY OF THE CITY MASTER TABLE

TC ID

TEST CASE Check the chain id for 1 data validation

2 check for referential integrity of state master 3 table 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

VALIDATION Should allow only entry to integer data (0-9) Should allow only entry to integer data (0-9)

TEST DATA

EXPECTED RESULT should not accept the test data It should accept the integer value

Enter A-Z,a-z,)

Enter (0-9)

ACTUAL RESULT SUCCESS/FAILURE

REMARKS/SUGGESS IONS

ATM

PAYPAL

1) test for ball or ink pen. 2) test for ink color (blue, red, what) 3) write with pen to see whether it works or not 4) check brand name and logo 5) check for body color 6) check for body material 7) drop pen from a reasonable height 8) check whether it is a click pen, or a pen with cap? 9) check for pen weight 10) check the refill

Test cases for Lift Hi, Lift are always as per requiremnts. So, It will not better to start with test cases without requirements.

Here I am taking the simplest example of metro rail lift used to get from Ticket floor (TF) to Platform floor (PF). Requiremen 1) When light is on for the lift and no request has been made to go from TF to PF, button light should Off. 2) When passanger made request for PF, button light should ON. 3) When button light is ON and if lift is available at TF, the door should open.

4) When button light is ON and if lift is not available at TF, the indicator light should indicate the movement of lift from PF to 5) When door opens, it should made a sound. 6) When passanger is in the lift, if passanger press the hold button lift door should not close. 7) If pasanger press the lift close button, it should close immediately otherwise should close automatically after fixed time. 8) If lift fan is ON, and passanger press FAN button it should get OFF or vice versa. 9) Try to call using CALL button to help persons using lift. 10) Now test for overload, if lift is for 10 persons or 100KG weight, try for 11 or 12 persons to use the lift at one time. 11) Lift door should not open when lift is moving, even after pressing lift opening button. 12) Try to use Pass button of the lift to overcome an request. 13) Let lift is at PF, it should not move to TF if no request made at TF and vice versa. 14) Let passanger get in lift from TF anf starts moving to PF, then if other request made to PF, then lift should complete first 15) If electricity get gone, Lift should not make a major jerks and starts working on emergency backup.

Friends, there can be above 100 test cases depending on requirement. I just write the major test cases for simplest lift requ

Hi, Here are the test cases for Bulb:1) Check for company logo. 2) Check for wattage marked. 3) Test with wattage plus/minus one, as per capacity of bulb. 4) Test for shape of the bulb. 5) Test for performance of the bulb by leaving it ON for more than 50 hours. 6) Test bulb life. 7) Test performance of bulb power up/down. 8) Test for bulb holder compatibility. 9) Test for bulb filament. 10) Test for holder metal used.

Test case for Date format month/date/year Test case for Date field can be:1) test format which is allowed like mm/dd/yy or MM/DD/YYYY or which one allowed. 2)Test for boundary values for date and month. 3) Test For null date /month/year 4) negatine date/month/year 5)Check for 30th feb like this more will depend on your scenario, whether any date is allowed or only user with 18+ is allowed etc.

1. Machine is accepting ATM card 2. Machine is rejecting expired card 3. successful entry of PIN number 4. unsuccessful operation due to enter wrong PIN number 3 times 5. successful selection of language 6. successful selection of account type 7. unsuccessful operation due to invalid account type 8. successful selection of amount to be withdraw 9. successful withdrawal. 10. Expected message due to amount is greater than day limit 11. unsuccessful withdraw operation due to lack of money in ATM 12. Expected message due to amount to withdraw is greater than possible balance. 13. unsuccessful withdraw operation due to click cancel after insert card

Test cases for payment gateway: My example is PayPal manager based:1) Test with valid card number with valid expiry but invalid CVV. 2) Test with valid card number with invalid expiry but valid CVV. 3) Test with valid card number with invalid expiry and CVV. 4) Test with valid details of expired/blocked card. 5) Test with valid card number, CVV and expiry date. 6) Test for reference transaction. 7) Test for billing/shipping details in payment manager. 8) Test for back payment to customer. 9) Test for "0" transaction. 10) Test for negative transaction. Write 10 test cases for Pen? 1) test for ball or ink pen. 2) test for ink color (blue, red, what) 3) write with pen to see whether it works or not 4) check brand name and logo 5) check for body color 6) check for body material 7) drop pen from a reasonable height 8) check whether it is a click pen, or a pen with cap? 9) check for pen weight 10) check the refill

Test cases for Lift Hi, Lift are always as per requiremnts. So, It will not better to start with test cases without requirements.

Here I am taking the simplest example of metro rail lift used to get from Ticket floor (TF) to Platform floor (PF). Requirement is passange 1) When light is on for the lift and no request has been made to go from TF to PF, button light should Off. 2) When passanger made request for PF, button light should ON. 3) When button light is ON and if lift is available at TF, the door should open.

4) When button light is ON and if lift is not available at TF, the indicator light should indicate the movement of lift from PF to TF. 5) When door opens, it should made a sound. 6) When passanger is in the lift, if passanger press the hold button lift door should not close. 7) If pasanger press the lift close button, it should close immediately otherwise should close automatically after fixed time. 8) If lift fan is ON, and passanger press FAN button it should get OFF or vice versa. 9) Try to call using CALL button to help persons using lift. 10) Now test for overload, if lift is for 10 persons or 100KG weight, try for 11 or 12 persons to use the lift at one time. 11) Lift door should not open when lift is moving, even after pressing lift opening button. 12) Try to use Pass button of the lift to overcome an request. 13) Let lift is at PF, it should not move to TF if no request made at TF and vice versa. 14) Let passanger get in lift from TF anf starts moving to PF, then if other request made to PF, then lift should complete first request first 15) If electricity get gone, Lift should not make a major jerks and starts working on emergency backup.

Friends, there can be above 100 test cases depending on requirement. I just write the major test cases for simplest lift requirement. Plea

Hi, Here are the test cases for Bulb:1) Check for company logo. 2) Check for wattage marked. 3) Test with wattage plus/minus one, as per capacity of bulb. 4) Test for shape of the bulb. 5) Test for performance of the bulb by leaving it ON for more than 50 hours. 6) Test bulb life. 7) Test performance of bulb power up/down. 8) Test for bulb holder compatibility. 9) Test for bulb filament. 10) Test for holder metal used.

Test case for Date format month/date/year Test case for Date field can be:1) test format which is allowed like mm/dd/yy or MM/DD/YYYY or which one allowed. 2)Test for boundary values for date and month. 3) Test For null date /month/year 4) negatine date/month/year 5)Check for 30th feb like this more will depend on your scenario, whether any date is allowed or only user with 18+ is allowed etc.

oor (TF) to Platform floor (PF). Requirement is passanger should able to use lift to go and come back from Ticket floor to platform floor. Precondition is passanger is on

uld indicate the movement of lift from PF to TF.

hould close automatically after fixed time.

2 persons to use the lift at one time.

t made to PF, then lift should complete first request first and come back to TF after PF.

e the major test cases for simplest lift requirement. Please comment if any query.

user with 18+ is allowed etc.

k from Ticket floor to platform floor. Precondition is passanger is on TF.