Testing Documentation for CCIH Database Management System By: John Reeves, Derek King, and Robert Watts
The testing process for our project is divided into three parts of Unit testing, one part of Integration/Function testing, and one part which combines the processes of System testing and Customer/User testing. In addition, a small number of System tests are added in a separate section to facilitate simple browser testing. To give this process additional structure, we have divided one of the two modules into “success cases” and “failure/error cases”. In order to better show how the test cases below are organized, the following diagram was created:
Below is the Unit Test Cases #1 list for the “Results Screen Error Inputs” Results Screen Error Inputs
ID # Description Text to input Result Description
1 grpno entered too long 123456 Report datatype numeric(5) error from database
2 grpno entered is empty Report not-null constraint from database
3 grpno entered non numeric Alpha Report datatype numeric(5) error from database
4 groupname entered too long ALPHABINGOCHARLIEDELTAECHOFOXTROTGOLFINDIA
Report datatype character varying(40) error from database
5 groupname entered is empty Report not-null constraint from database
6 state entered too long KYA Report datatype character(2) error from database
7 claim_charge is non numeric Alpha Report datatype numeric(14, 4) error from database
8 claim_charge is too long after the decimal 12.00001 Report datatype numeric(14, 4) error from database
9 claim charge is too long before the decimal 12345678901.1 Report datatype numeric(14, 4) error from database
10 clmpre is too long 12345 Report datatype numeric(4) error from database
11 clmpre is empty Report not-null constraint from database
12 clmpre is non numeric Alp Report datatype numeric(4) error from database
13 clmno is too long 1234567890 Report datatype numeric(9) error from database
14 clmno is non numeric Alpha Report datatype numeric(9) error from database
15 lockno is too long 1 Report datatype numeric(10) error from database
16 lockno is non numeric Alpha Report datatype numeric(10) error from database
17 fromdt contains wrong format #1 AB-JAN-2012 Report datatype date error from database
18 fromdt contains wrong format #2 12, Jan 2012 Report datatype date error from database
19 fromdt contains wrong format #3 12 Jan, 2012, Jan Report datatype date error from database
20 fromdt contains wrong format #4 asldfj Report datatype date error from database
21 fromdt does not exist #1 13/13/2012 Report datatype date error from database
22 fromdt does not exist #2 0/0/2012 Report datatype date error from database
23 active entered is not a valid boolean K Report datatype Boolean error from database
24 active entered is not a valid boolean TRUEA Report datatype Boolean error from database
Below is the Unit Test Cases #2 list for the “Search Query Screen All Input Types.” Search Query Screen Testing (All Cases)
ID# Description Text to input ('|' indicates separate text box fields) Result Description
1 Testing Client Search Function (one field)
client: 300 | claims: | | PPO: invoice: | |
Result Screen with Client Columns where (GRPNO = 300)
2 Testing Client Search Function (no results)
client: 77 | claims: | | PPO:
invoice: | | Result Screen : "no results found"
3 Testing PPO Search Function (one field)
client: | claims: | | PPO: 0 invoice: | |
Result Screen with PPO Columns where (PPONO = 0)
4 Testing PPO Search Function (no results)
client: | claims: | | PPO: 77
invoice: | | Result Screen : "no results found"
5 Testing Claims Search Function (one field)
client: |
claims: | 345001047 | PPO:
invoice: | |
Result Screen with Claims Columns where (CLMNO = 345001047)
6 Testing Claims Search Function (all fields)
client: |
claims: 2015 | 345001047 | 0 PPO:
invoice: | |
Result Screen with Claims Columns where (CLMPRE = 2015) AND (CLMNO =
345001047) AND (CLMSUF = 0)
7 Testing Claims Search Function (no results)
client: | claims: | | PPO:
8 Testing Invoices Search Function (one field)
client: | claims: | | PPO: invoice: 300 | |
Result Screen with Claims Columns where (GRPNO = 300)
9 Testing Invoices Search Function (all fields)
client: | claims: | | PPO: invoice: 300 | 1 | 0
Result Screen with Invoices Columns where (GRPNO = 300) AND (LOCNO = 1) AND (PPONO = 0)
10 Testing Invoices Search Function (no results)
client: | claims: | | PPO:
invoice: 77 | | Result Screen : "no results found"
11 Testing Client and PPO (all fields and results)
client: 300 | claims: | | PPO: 0 invoice: | |
Result Screen with Client and PPO columns where (client.GRPNO = 300) AND (ppo.PPONO = 0)
12 Testing Client and Claims (all fields and results)
client: 300 | claims: 2015 | | PPO: invoice: | |
Result Screen with Client and Claims columns where (client.GRPNO = 300) AND (claim.CLMPRE = 2015)
13 Testing Client and Invoices (all fields and results)
client: 300 | claims: | | PPO: invoice: 300 | |
Result Screen with Client and Invoice columns where (client.GRPNO = 300) AND (invoice.GRPNO = 300)
14 Testing Claims and PPO (all fields and results)
client: | claims: 2015 | | PPO: 0 invoice: | |
Result Screen with Claim and PPO columns where (claim.CLMPRE = 2015) AND (ppo.PPONO = 0)
client: | claims: | | PPO: 0
Result Screen with Invoice and PPO columns where (invoice.GRPNO = 300)
16 Testing Invoices and Claims (all fields and results)
client: | claims: 2015 | | PPO: invoice: 300 | |
Result Screen with Invoice and Claims columns where (invoice.GRPNO = 300) AND (claims.CLMPRE = 2015)
17 Testing Client, Claims, and PPO (all fields and results)
client: 300 | claims: 2015 | | PPO: 0 invoice: | |
Result Screen with Client, Claims, and PPO columns where (client.GRPNO = 300) AND (claims.CLMPRE = 2015) AND (ppo.PPONO = 0)
18
Testing Client, Claims, and Invoices (all fields and results)
client: 300 | claims: 2015 | | PPO: invoice: 300 | |
Result Screen with Client, Claims, and Invoice columns where (client.GRPNO = 300) AND (claims.CLMPRE = 2015) AND (invoice.GRPNO = 300)
19
Testing Client, Invoices, and PPO (all fields and results)
client: 300 | claims: | | PPO: 0 invoice: 300 | |
Result Screen with Client, PPO, and Invoice columns where (client.GRPNO = 300) AND (ppo.PPONO = 0) AND (invoice.GRPNO = 300)
20
Testing Invoices, Claims, and PPO (all fields and results)
client: | claims: 2015 | | PPO: 0 invoice: 300 | |
Result Screen with PPO, Claims, and Invoice columns where (ppo.PPONO) AND (claims.CLMPRE = 2015) AND (invoice.GRPNO = 300)
21 Testing all Search functions (all fields and results)
client: 300 | claims: 2015 | | PPO: 0 invoice: 300 | |
Result Screen with Client, PPO, Claims, and Invoice columns where (ppo.PPONO) AND (claims.CLMPRE = 2015) AND (invoice.GRPNO = 300) AND (client.GRPNO = 300)
Below is the Unit Test Cases #3 list for the “Results Screen Success Inputs.” They can be accessed during the Unit Test Cases #1 phase, and can be performed in any order.
Results Screen Success Inputs
ID# Description Text to input Result Description
1 grpno entered as minimum length 1 Database returns '1 rows affected'
2 grpno entered as maximum length 12345 Database returns '1 rows affected'
3 groupname entered as minimum length A Database returns '1 rows affected'
4 groupname entered as maximum length ALPHABINGOCHARLIEDELTAECHOFOXTROTGOLFINDI Database returns '1 rows affected'
5 state entered as minimum length K Database returns '1 rows affected'
6 state entered as maximum length KY Database returns '1 rows affected'
7 claim_charge entered as minimum length 1 Database returns '1 rows affected'
8 claim_charge entered as maximum length 1234567890.0123 Database returns '1 rows affected'
9 clmpre is entered as minimum length 1 Database returns '1 rows affected'
10 clmpre is entered as maximum length 1234 Database returns '1 rows affected'
11 clmno is entered as minimum length 1 Database returns '1 rows affected'
12 clmno is entered as maximum length 123456789 Database returns '1 rows affected'
13 lockno is entered as minimum length 1 Database returns '1 rows affected'
14 lockno is entered as maximum length 1234567890 Database returns '1 rows affected'
15 fromdt is entered as Dec-31 in format #1 12/31/2016 Database returns '1 rows affected'
16 fromdt is entered as Dec-31 in format #2 31-Dec-16 Database returns '1 rows affected'
17 active entered as True TRUE Database returns '1 rows affected'
19 active entered as T T Database returns '1 rows affected'
20 active entered as F F Database returns '1 rows affected'
21 ppo_method is entered as 's' s Database returns '1 rows affected'
22 ppo_method is entered as 'd' d Database returns '1 rows affected'
23
ppo_method is entered as 's' AND grpno is entered as maximum length
s
12345 Database returns '2 rows affected'
24
ppo_method is entered as 's' AND grpno is entered as maximum length AND active entered as True
s 12345
Below is the System Test Cases list. It simply tests the program on each of the three popular web browsers set out in our design. FireFox, Internet Explorer, and Google Chrome testing
Success
ID # Description Text to input ('|' indicates separate text box fields) Result Description
1
USING FIREFOX WEB BROWSER ppo_method is entered as 's' AND grpno is entered as maximum length AND active entered as True
s 12345
True Database returns '3 rows affected'
2
USING INTERNET EXPLORER WEB BROWSER ppo_method is entered as 's' AND grpno is entered as maximum length AND active entered as True
s 12345
True Database returns '3 rows affected'
3
USING GOOGLE CHROME WEB BROWSER
ppo_method is entered as 's' AND grpno is entered as maximum length AND active entered as True
s 12345
True Database returns '3 rows affected'
Finally, for regression testing we must begin from the beginning of the list and do all sections in sequence.
All tests are to be repeated once the program is installed upon the client’s system, this repetition accomplishes System testing. Once system testing is complete the client will have open ended access to test the program in any way that they see fit. This last type of testing is called User or Customer Testing.
