Download Report

106
APPENDIX C. TEST OF CHECKS DONE BY VISITORS IN 3E
All specified transaction-attributes are
specified to be ’Required’, ’RequiresNew’
or ’Mandatory’
No errors
As expected
Test: The type of server is always ’JBoss’ or ’WebLogice6.1’
Input data
Expected result
Test result
The type of server is specified be ’Bea’
IllegalInputException:
’TypeOfServer
match ’jBoss’ or ’webLogic6.1’ ’
must
As expected
The type of server is specified be ’weblogic61’
IllegalInputException:
’TypeOfServer
match ’jBoss’ or ’webLogic6.1’ ’
must
As expected
Type of server specified to be ’Jboss’
No errors
As expected
Type of server specified to be ’jboss’
No errors
As expected
Type of server specified to be ’WebLogic6.1’
No errors
As expected
Test: The multiplicity of each role in relation must be exactly ’One’ or ’Many’
Input data
Expected result
Test result
Multiplicity for role cruise-belongs-to-ship
in relation Cruise_Ship is specified to be
’two’
IllegalInputException: ’Multiplicity for Role
cruise-belongs-to-ship in relation Cruise_Ship
MUST be exactly ’One’ or ’Many’. Is two’
Gave VisitorErrorException
Multiplicity for role cruise-belongs-to-ship
in relation Cruise_Ship is specified to be
’one’
IllegalInputException: ’Multiplicity for Role
cruise-belongs-to-ship in relation Cruise_Ship
MUST be exactly ’One’ or ’Many’. Is one’
Gave VisitorErrorException
Multiplicity for role cruise-belongs-to-ship
in relation Cruise_Ship is specified to be
’many’
IllegalInputException: ’Multiplicity for Role
cruise-belongs-to-ship in relation Cruise_Ship
MUST be exactly ’One’ or ’Many’. Is many’
Gave VisitorErrorException
Multiplicity for role specified to be ’One’
No errors
As expected
Multiplicity for role specified to be ’Many’
No errors
As expected