Download presentation
Presentation is loading. Please wait.
1
Test Case Items February, 2019
2
Problem Need to fix things in some test cases
Need to adjust some things in the specification
3
QS-M-2-20 Problem - Incorrect type Solution – Correct the type
-40,7 +40,7 <Operation type="Enumeration" value="Create"/> <ResultStatus type="Enumeration" value="OperationFailed"/> <ResultReason type="Enumeration" value="GeneralFailure"/> - <ResultMessage type="Enumeration" value="NOT_SAFE"/> + <ResultMessage type="TextString" value="NOT_SAFE"/> <ResponsePayload> </ResponsePayload> </BatchItem>
4
QS-M-2-20 Problem – Empty response payload on error
Solution – Remove it – it should not be present -41,8 +41,6 <ResultStatus type="Enumeration" value="OperationFailed"/> <ResultReason type="Enumeration" value="GeneralFailure"/> <ResultMessage type="TextString" value="NOT_SAFE"/> - <ResponsePayload> - </ResponsePayload> </BatchItem> </ResponseMessage>
5
BL-M-2-20 Problem – Typo in Interop Identifier
Solution – Correct it – in both places -14,7 +14,7 <Operation type="Enumeration" value="Interop"/> <RequestPayload> <InteropFunction type="Enumeration" value="Begin"/> <InteropIdentifier type="TextString" value="BL-M-2-10"/> <InteropIdentifier type="TextString" value="BL-M-2-20"/> </RequestPayload> </BatchItem> </RequestMessage> -218,7 +218,7 <InteropFunction type="Enumeration" value="End"/>
6
TC-LOGIN-2-20 Problem – Error in return – missing Operation
Solution – Correct it -297,7 +297,8 <BatchCount type="Integer" value="1"/> </ResponseHeader> <BatchItem> - <ResultStatus type="Enumeration" value="OperationSuccess"/> + <Operation type="Enumeration" value="Interop"/> + <ResultStatus type="Enumeration" value="Success"/> <ResponsePayload> </ResponsePayload> </BatchItem>
7
TC-LOGIN-3-20 Problem – Error in return – missing Operation
Solution – Correct it -340,7 +340,8 <BatchCount type="Integer" value="1"/> </ResponseHeader> <BatchItem> - <ResultStatus type="Enumeration" value="OperationSuccess"/> + <Operation type="Enumeration" value="Interop"/> + <ResultStatus type="Enumeration" value="Success"/> <ResponsePayload> </ResponsePayload> </BatchItem>
8
TC-LOGIN-2-20 Problem – Error in return – missing Operation
Solution – Correct it -261,6 +261,7 <BatchCount type="Integer" value="1"/> </ResponseHeader> <BatchItem> + <Operation type="Enumeration" value="Query"/> <ResultStatus type="Enumeration" value="OperationFailed"/> <ResultReason type="Enumeration" value="InvalidTicket"/> <ResultMessage type="TextString" value="Kmip"/>
9
TC-LOGIN-2-20 Problem – Test Case / Specification Difference
Solution – Correct Specification – matches intent (note – in three locations in this test case) -90,8 +90,10 <Credential> <CredentialType type="Enumeration" value="Ticket"/> <CredentialValue> <Ticket> <TicketType type="Enumeration" value="Login"/> <TicketValue type="ByteString" value="$TICKET_VALUE"/> </Ticket> </CredentialValue> </Credential> </Authentication>
10
PKCS11-M-1-20 Problem – Test Case contains non-required item
Solution – Correct it – correlation value is non-meaningful after C_Finalize call -111,7 +111,6 <ResultStatus type="Enumeration" value="Success"/> <ResponsePayload> <PKCS_11Function type="Enumeration" value="C_Finalize"/> <CorrelationValue type="ByteString" value="$CORRELATION_VALUE"/> <PKCS_11ReturnCode type="Enumeration" value="OK"/> </ResponsePayload> </BatchItem>
11
TC-IMPEXP-1-20 Problem – Test Case contains incorrect Fresh
Solution – Correct it – export does not alter Fresh and we should update the specification to make that clearer -139,7 +139,7 <InitialDate type="DateTime" value=" T19:24:26+10:00"/> <State type="Enumeration" value="PreActive"/> <LastChangeDate type="DateTime" value=" T19:24:26+10:00"/> <Fresh type="Boolean" value="false"/> <Fresh type="Boolean" value="true"/> <Sensitive type="Boolean" value="false"/> <AlwaysSensitive type="Boolean" value="false"/> <Extractable type="Boolean" value="true"/>
12
TC-IMPEXP-2-20 Problem – Test Case contains incorrect Fresh
Solution – Correct it – export does not alter Fresh and we should update the specification to make that clearer -139,7 +139,7 <InitialDate type="DateTime" value=" T19:24:26+10:00"/> <State type="Enumeration" value="PreActive"/> <LastChangeDate type="DateTime" value=" T19:24:26+10:00"/> <Fresh type="Boolean" value="false"/> <Fresh type="Boolean" value="true"/> <Sensitive type="Boolean" value="false"/> <AlwaysSensitive type="Boolean" value="false"/> <Extractable type="Boolean" value="true"/> -194,7 +194,7 <ActivationDate type="DateTime" value=" T00:00:00+10:00"/> <State type="Enumeration" value="Active"/>
13
TC-IMPEXP-3-20 Problem – Test Case contains incorrect Fresh
Solution – Correct it – export does not alter Fresh and we should update the specification to make that clearer -135,7 +135,7 <State type="Enumeration" value="PreActive"/> <ProtectStopDate type="DateTime" value=" T00:00:00+10:00"/> <LastChangeDate type="DateTime" value=" T19:24:26+10:00"/> <Fresh type="Boolean" value="false"/> <Fresh type="Boolean" value="true"/> <Sensitive type="Boolean" value="false"/> <AlwaysSensitive type="Boolean" value="false"/> <Extractable type="Boolean" value="true"/> -186,7 +186,7 -272,7 +272,7
14
TC-IMPEXP-4-20 Problem – Test Case contains incorrect Fresh
Solution – Correct it – export does not alter Fresh and we should update the specification to make that clearer -151,7 +151,7 <InitialDate type="DateTime" value=" T19:24:26+10:00"/> <State type="Enumeration" value="PreActive"/> <LastChangeDate type="DateTime" value=" T19:24:26+10:00"/> <Fresh type="Boolean" value="false"/> <Fresh type="Boolean" value="true"/> <Sensitive type="Boolean" value="false"/> <AlwaysSensitive type="Boolean" value="false"/> <Extractable type="Boolean" value="true"/> -256,7 +256,7 -360,7 +360,7
15
TC-IMPEXP-5-20 Problem – Test Case contains incorrect Fresh
Solution – Correct it – export does not alter Fresh and we should update the specification to make that clearer -144,7 +144,7 <InitialDate type="DateTime" value=" T19:24:27+10:00"/> <State type="Enumeration" value="PreActive"/> <LastChangeDate type="DateTime" value=" T19:24:27+10:00"/> <Fresh type="Boolean" value="false"/> <Fresh type="Boolean" value="true"/> <Sensitive type="Boolean" value="false"/> <AlwaysSensitive type="Boolean" value="false"/> <Extractable type="Boolean" value="true"/> -218,7 +218,7
16
MSGENC-HTTPS-M-1-20 Problem – Test Case has ClientCorrelationValue in wrong location Solution – Correct it -51,8 +51,8 <ProtocolVersionMajor type="Integer" value="2"/> <ProtocolVersionMinor type="Integer" value="0"/> </ProtocolVersion> - <ClientCorrelationValue type="TextString" value="MSGENC-HTTPS-M-1-20 step=1"/> <MaximumResponseSize type="Integer" value="2048"/> + <ClientCorrelationValue type="TextString" value="MSGENC-HTTPS-M-1-20 step=1"/> <BatchCount type="Integer" value="1"/> </RequestHeader> <BatchItem>
17
MSGENC-JSON-M-1-20 Problem – Test Case has ClientCorrelationValue in wrong location Solution – Correct it -51,8 +51,8 <ProtocolVersionMajor type="Integer" value="2"/> <ProtocolVersionMinor type="Integer" value="0"/> </ProtocolVersion> - <ClientCorrelationValue type="TextString" value="MSGENC-HTTPS-M-1-20 step=1"/> <MaximumResponseSize type="Integer" value="2048"/> + <ClientCorrelationValue type="TextString" value="MSGENC-HTTPS-M-1-20 step=1"/> <BatchCount type="Integer" value="1"/> </RequestHeader> <BatchItem>
18
MSGENC-XML-M-1-20 Problem – Test Case has ClientCorrelationValue in wrong location Solution – Correct it -51,8 +51,8 <ProtocolVersionMajor type="Integer" value="2"/> <ProtocolVersionMinor type="Integer" value="0"/> </ProtocolVersion> - <ClientCorrelationValue type="TextString" value="MSGENC-HTTPS-M-1-20 step=1"/> <MaximumResponseSize type="Integer" value="2048"/> + <ClientCorrelationValue type="TextString" value="MSGENC-HTTPS-M-1-20 step=1"/> <BatchCount type="Integer" value="1"/> </RequestHeader> <BatchItem>
19
XML and JSON Problem – time values without time zone
Solution – note it during testing – not permitted as the other party does not know the time zone settings and cannot adjust T06:09:36+00:00 T06:09:36Z T06:00:36+09:00 T06:09:36
20
Interop Operation Problem – only a subset of 2.0 tests used it
Solution – require it for all tests for interop BL-M-{1..13}-20 TC-LOGIN-{1..3}-20 TC-DLOGIN-{1..3}-20 TC-IMPEXP-{1..5}-20 TC-SETATTR-{1..3}-20 i.e. 27 out of the 188 defined test cases
21
Conclusion Simple updates from latest interop
General consensus that testing went well Were things were handled differently for specific test cases – either interpretation was accepted during interop
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.