Testing Documentation for CCIH Database Management System By: John Reeves, Derek King, and Robert Watts

Transcription

1 Teting Documentation for CCIH Databae Management Sytem By: John Reeve, Derek King, and Robert Watt The teting proce for our project i divided into three part of Unit teting, one part of Integration/Function teting, and one part which combine the procee of Sytem teting and Cutomer/Uer teting. In addition, a mall number of Sytem tet are added in a eparate ection to facilitate imple brower teting. To give thi proce additional tructure, we have divided one of the two module into ucce cae and failure/error cae. In order to better how how the tet cae below are organized, the following diagram wa created: 1

2 Below i the Unit Tet Cae #1 lit for the Reult Screen Error Input Reult Screen Error Input ID # Decription Text to input Reult Decription 1 grpno entered too long Report datatype numeric(5) error from databae 2 grpno entered i empty Report not-null contraint from databae 3 grpno entered non numeric Alpha Report datatype numeric(5) error from databae 4 groupname entered too long ALPHABINGOCHARLIEDELTAECHOFOXTROTGOLFINDIA Report datatype character varying(40) error from databae 5 groupname entered i empty Report not-null contraint from databae 6 tate entered too long KYA Report datatype character(2) error from databae 7 claim_charge i non numeric Alpha Report datatype numeric(14, 4) error from databae 8 claim_charge i too long after the decimal Report datatype numeric(14, 4) error from databae 9 claim charge i too long before the decimal Report datatype numeric(14, 4) error from databae 10 clmpre i too long Report datatype numeric(4) error from databae 11 clmpre i empty Report not-null contraint from databae 12 clmpre i non numeric Alp Report datatype numeric(4) error from databae 13 clmno i too long Report datatype numeric(9) error from databae 14 clmno i non numeric Alpha Report datatype numeric(9) error from databae 15 lockno i too long 1 Report datatype numeric(10) error from databae 16 lockno i non numeric Alpha Report datatype numeric(10) error from databae 17 fromdt contain wrong format #1 AB-JAN-2012 Report datatype date error from databae 18 fromdt contain wrong format #2 12, Jan 2012 Report datatype date error from databae 19 fromdt contain wrong format #3 12 Jan, 2012, Jan Report datatype date error from databae 20 fromdt contain wrong format #4 aldfj Report datatype date error from databae 21 fromdt doe not exit #1 13/13/2012 Report datatype date error from databae 22 fromdt doe not exit #2 0/0/2012 Report datatype date error from databae 23 active entered i not a valid boolean K Report datatype Boolean error from databae 24 active entered i not a valid boolean TRUEA Report datatype Boolean error from databae 25 ppo_method i too long AA Report datatype character(1) error from databae 26 ppo_method not '' or 'd' a Report content error 2

3 Below i the Unit Tet Cae #2 lit for the Search Query Screen All Input Type. Search Query Screen Teting (All Cae) ID# Decription Text to input (' ' indicate eparate text box field) Reult Decription 1 Teting Client Search Function (one field) 2 Teting Client Search Function (no reult) 3 Teting PPO Search Function (one field) 4 Teting PPO Search Function (no reult) 5 Teting Claim Search Function (one field) 6 Teting Claim Search Function (all field) 7 Teting Claim Search Function (no reult) Reult Screen with Client Column where (GRPNO = 300) client: 77 Reult Screen : "no reult found" 0 Reult Screen with PPO Column where (PPONO = 0) 77 Reult Screen : "no reult found" claim: claim: Reult Screen with Claim Column where (CLMNO = ) Reult Screen with Claim Column where (CLMPRE = 2015) (CLMNO = ) (CLMSUF = 0) Reult Screen : "no reult found" 3

4 8 Teting Invoice Search Function (one field) 9 Teting Invoice Search Function (all field) 10 Teting Invoice Search Function (no reult) invoice: Reult Screen with Claim Column where (GRPNO = 300) Reult Screen with Invoice Column where (GRPNO = 300) (LOCNO = 1) (PPONO = 0) invoice: 77 Reult Screen : "no reult found" 11 Teting Client and PPO (all field and reult) 12 Teting Client and Claim (all field and reult) 13 Teting Client and Invoice (all field and reult) 14 Teting Claim and PPO (all field and reult) 15 Teting Invoice and PPO (all field and reult) Reult Screen with Client and PPO column where (client.grpno = 300) (ppo.ppono = 0) Reult Screen with Client and Claim column where (client.grpno = 300) (claim.clmpre = 2015) Reult Screen with Client and Invoice column where (client.grpno = 300) (invoice.grpno = 300) Reult Screen with Claim and PPO column where (claim.clmpre = 2015) (ppo.ppono = 0) Reult Screen with Invoice and PPO column where (invoice.grpno = 300) (ppo.ppono = 0) 4

5 16 Teting Invoice and Claim (all field and reult) Reult Screen with Invoice and Claim column where (invoice.grpno = 300) (claim.clmpre = 2015) 17 Teting Client, Claim, and PPO (all field and reult) Teting Client, Claim, and Invoice (all field and reult) Teting Client, Invoice, and PPO (all field and reult) Teting Invoice, Claim, and PPO (all field and reult) 21 Teting all Search function (all field and reult) Reult Screen with Client, Claim, and PPO column where (client.grpno = 300) (claim.clmpre = 2015) (ppo.ppono = 0) Reult Screen with Client, Claim, and Invoice column where (client.grpno = 300) (claim.clmpre = 2015) (invoice.grpno = 300) Reult Screen with Client, PPO, and Invoice column where (client.grpno = 300) (ppo.ppono = 0) (invoice.grpno = 300) Reult Screen with PPO, Claim, and Invoice column where (ppo.ppono) (claim.clmpre = 2015) (invoice.grpno = 300) Reult Screen with Client, PPO, Claim, and Invoice column where (ppo.ppono) (claim.clmpre = 2015) (invoice.grpno = 300) (client.grpno = 300) 5

6 Below i the Unit Tet Cae #3 lit for the Reult Screen Succe Input. They can be acceed during the Unit Tet Cae #1 phae, and can be performed in any order. Reult Screen Succe Input ID# Decription Text to input Reult Decription 1 grpno entered a minimum length 1 Databae return '1 row affected' 2 grpno entered a maximum length Databae return '1 row affected' 3 groupname entered a minimum length A Databae return '1 row affected' 4 groupname entered a maximum length ALPHABINGOCHARLIEDELTAECHOFOXTROTGOLFINDI Databae return '1 row affected' 5 tate entered a minimum length K Databae return '1 row affected' 6 tate entered a maximum length KY Databae return '1 row affected' 7 claim_charge entered a minimum length 1 Databae return '1 row affected' 8 claim_charge entered a maximum length Databae return '1 row affected' 9 clmpre i entered a minimum length 1 Databae return '1 row affected' 10 clmpre i entered a maximum length 1234 Databae return '1 row affected' 11 clmno i entered a minimum length 1 Databae return '1 row affected' 12 clmno i entered a maximum length Databae return '1 row affected' 13 lockno i entered a minimum length 1 Databae return '1 row affected' 14 lockno i entered a maximum length Databae return '1 row affected' 15 fromdt i entered a Dec-31 in format #1 12/31/2016 Databae return '1 row affected' 16 fromdt i entered a Dec-31 in format #2 31-Dec-16 Databae return '1 row affected' 17 active entered a True TRUE Databae return '1 row affected' 18 active entered a Fale FALSE Databae return '1 row affected' 6

7 19 active entered a T T Databae return '1 row affected' 20 active entered a F F Databae return '1 row affected' 21 ppo_method i entered a '' Databae return '1 row affected' 22 ppo_method i entered a 'd' d Databae return '1 row affected' 23 ppo_method i entered a '' grpno i entered a maximum length Databae return '2 row affected' 24 ppo_method i entered a '' grpno i entered a maximum length active entered a True True Databae return '3 row affected' 7

8 Below i the Sytem Tet Cae lit. It imply tet the program on each of the three popular web brower et out in our deign. FireFox, Internet Explorer, and Google Chrome teting Succe ID # Decription Text to input (' ' indicate eparate text box field) Reult Decription 1 USING FIREFOX WEB BROWSER ppo_method i entered a '' grpno i entered a maximum length active entered a True True Databae return '3 row affected' 2 USING INTERNET EXPLORER WEB BROWSER ppo_method i entered a '' grpno i entered a maximum length active entered a True True Databae return '3 row affected' 3 USING GOOGLE CHROME WEB BROWSER ppo_method i entered a '' grpno i entered a maximum length active entered a True True Databae return '3 row affected' Finally, for regreion teting we mut begin from the beginning of the lit and do all ection in equence. All tet are to be repeated once the program i intalled upon the client ytem, thi repetition accomplihe Sytem teting. Once ytem teting i complete the client will have open ended acce to tet the program in any way that they ee fit. Thi lat type of teting i called Uer or Cutomer Teting. 8