Wiki Navigation

Automated Test Case Results
1. Test Run Summary
2. Individual Test Run Details

Automated Test Case Results

Test Run Summary

Comments about this Test Run

Validation against schema still not working correctly. All tests failing with schema validation are not confirmed as Failed
Selector test cases are failing due to script errors
Some tests are failing because of different providers and class names running on the test system
Some tests are failing, although they are not MUST rules

Test Cases and Results

1. ./tests/Discovery/rmcp	Failed
2. ./tests/Discovery/validIdentify	Warning
3. ./tests/Discovery/validIdentifyWithActionHeader	Passed
4. ./tests/Transport/ClassA	Failed
5. ./tests/Transport/ClassB	Info
6. ./tests/WS-Protocol/Action/InvalidAction	Passed
7. ./tests/WS-Protocol/Action/missingAction	Passed
8. ./tests/WS-Protocol/Action/validAction	Passed
9. ./tests/WS-Protocol/BasicEnumerate	Passed
10. ./tests/WS-Protocol/BasicGet	Failed
11. ./tests/WS-Protocol/EnumAllClassURI	Failed
12. ./tests/WS-Protocol/EnumClassURI	Passed
13. ./tests/WS-Protocol/EnumCount	Passed
14. ./tests/WS-Protocol/EnumExpiresTimeOut	Passed
15. ./tests/WS-Protocol/EnumModeEPR	Failed
16. ./tests/WS-Protocol/EnumModeObjectEPR	Failed
17. ./tests/WS-Protocol/EnumOptimize	Passed
18. ./tests/WS-Protocol/EnumPolymorphismAllClass	Failed
19. ./tests/WS-Protocol/EnumPolymorphismExclude	Passed
20. ./tests/WS-Protocol/EnumPolymorphismInclude	Failed
21. ./tests/WS-Protocol/EnumPolymorphismNone	Passed
22. ./tests/WS-Protocol/FaultEncoding	Passed
23. ./tests/WS-Protocol/From/mustUnderstandFalse	Passed
24. ./tests/WS-Protocol/From/mustUnderstandTrue	Passed
25. ./tests/WS-Protocol/GetBaseInstance	Warning
26. ./tests/WS-Protocol/GetDerivedInstance	Failed
27. ./tests/WS-Protocol/GetFragment	Failed
28. ./tests/WS-Protocol/Locale/mustUnderstandFalse	Passed
29. ./tests/WS-Protocol/Locale/mustUnderstandTrue	Info
30. ./tests/WS-Protocol/MaxEnvelope	Passed
31. ./tests/WS-Protocol/MsgIDRelatesTo/duplicateMsgId	Passed
32. ./tests/WS-Protocol/MsgIDRelatesTo/invalidMsgId	Failed
33. ./tests/WS-Protocol/MsgIDRelatesTo/missingMsgId	Passed
34. ./tests/WS-Protocol/MsgIDRelatesTo/MsgIdEqRelatesTo	Passed
35. ./tests/WS-Protocol/OperationTimeout/invalidValue	Warning
36. ./tests/WS-Protocol/OperationTimeout/validValue	Passed
37. ./tests/WS-Protocol/OptionSet/mustUnderstandFalse	Passed
38. ./tests/WS-Protocol/OptionSet/mustUnderstandTrue	Passed
39. ./tests/WS-Protocol/PullEOSRelease	Passed
40. ./tests/WS-Protocol/PullInvalidEnumContext	Passed
41. ./tests/WS-Protocol/PullInvalidEPR	Passed
42. ./tests/WS-Protocol/PullMaxCharGtMaxEnv	Passed
43. ./tests/WS-Protocol/PullMaxCharLtMaxEnv	Passed
44. ./tests/WS-Protocol/PullmissingEnumContext	Passed
45. ./tests/WS-Protocol/ReleaseInvalidEnumContext	Passed
46. ./tests/WS-Protocol/ReleaseInvalidEPR	Passed
47. ./tests/WS-Protocol/ReleaseMissingEnumContext	Passed
48. ./tests/WS-Protocol/ReleaseTimeOut	Passed
49. ./tests/WS-Protocol/ReplyTo/missingReplyTo	Passed
50. ./tests/WS-Protocol/ReplyTo/ReplyToEqWsaTo	Passed
51. ./tests/WS-Protocol/ReplyTo/ReplyToRefParam	Passed
52. ./tests/WS-Protocol/Selector/cimnamespace	Passed
53. ./tests/WS-Protocol/Selector/duplicateSelector	Failed
54. ./tests/WS-Protocol/Selector/invalidName	Failed
55. ./tests/WS-Protocol/Selector/missingSelector	Passed
56. ./tests/WS-Protocol/URI/invalidResourceURI	Passed
57. ./tests/WS-Protocol/URI/missingResourceURI	Passed
58. ./tests/WS-Protocol/URI/validResourceURI	Passed
59. ./tests/WS-Protocol/WsaTo/missingWsaTo	Passed
60. ./tests/WS-Protocol/WsaTo/mustUnderstandTrue/invalidWsaTo	Failed
61. ./tests/WS-Protocol/WsaTo/mustUnderstandTrue/validWsaTo	Passed
62. ./tests/WS-Protocol/WsaTo/validWsaTo	Passed

Test Case Summery Table

Server Model
Operating System
Operating System Version
Total number of test cases found	62
Total number of invalid test cases found	0
Total number of test cases executed	62
Total number of test cases passed	45
Total number of test cases failed	14
Total number of test cases warned	3
Total number of test cases unsupported	0
Pass Percentage	72.5806%
Fail Percentage	22.5806%
Warn Percentage	4.83871%
Start Time	Sat Mar 3 23:59:33 EST 2007
End Time	Sun Mar 4 00:08:06 EST 2007
Test Execution Time	-23 hrs : -51 mins: -27 secs

Individual Test Run Details

Test Case # 1

Test Case Description

Test Management Access Point(MAP) Discovery Stage One - RMCP presence Ping/Pong. The DMWG compliant MAP shall support Ping/Pong command on well-known UDP port (623).

Test Details

Test Directory

./tests/Discovery/rmcp

Basic Result Checking

Output doesn't conform with the Mandatory Requirements in the Specifications

Detailed Result Processing by using

./tests/Discovery/rmcp/runtest.sh

Test Run Output

RMCP Ping/Pong test fails

Final Result

FAIL

Test Case # 2

Test Case Description

R8.9-1: A WS-Management service SHOULD support the wsmid:Identify operation.

<1> Wsmid:IdentifyResponse/wsmid:ProtocolVersion: A required Element or elements, each of which is a URI whose value must be equal to the core XML namespanes identifying a supported version of the WS_Management

Test Details

Test Directory

./tests/Discovery/validIdentify

Basic Result Checking

Output conforms with the Specifications

Detailed Result Processing by using

./tests/Discovery/validIdentify/runtest.sh

Test Run Output

./tests/Discovery/validIdentify/runtest.sh: line 16: syntax error near unexpected token `<<<'
./tests/Discovery/validIdentify/runtest.sh: line 16: `<<<<<<< .mine'

Final Result

WARN

Test Case # 3

Test Case Description

/***R8.9-2***/: A service supporting the wsmid:Identify operation MUST NOT require the presence of any SOAP header elements in order to dispatch execution of the request. If a service receives a wsmid:Identify operation containing unexpected or unsupported header content with mustUnderstand set to "false", the service MUST NOT fault the request and MUST process the body of the request as though the header elements were not present

/*<1>*/ Wsmid:IdentifyResponse/wsmid:ProtocolVersion: A required Element or elements, each of which is a URI whose value must be equal to the core XML namespanes identifying a supported version of the WS_Management pecification.One element must be provided for each supported version

Test Details

Test Directory: ./tests/Discovery/validIdentifyWithActionHeader
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/Discovery/validIdentifyWithActionHeader/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 4

Test Case Description

Test DMWG HTTP 1.1 transport with ClassA security profile: HTTP Digest user authentication.

Test Details

Test Directory

./tests/Transport/ClassA

Basic Result Checking

Output doesn't conform with the Mandatory Requirements in the Specifications

Detailed Result Processing by using

./tests/Transport/ClassA/runtest.sh

Test Run Output

UTF-16 charset is not supported
DMWG ClassA invalid security profile validation fails

Final Result

FAIL

Test Case # 5

Test Case Description

Test DMWG HTTP 1.1 transport with ClassB HTTP_TLS_1 security profile: HTTP Digest user authentication with TLS 1.0 TLS_RSA_WITH_AES_128_CBC_SHA cipher suite supported.

Test Details

Test Directory

./tests/Transport/ClassB

Basic Result Checking

Output conforms with the Specifications

Detailed Result Processing by using

./tests/Transport/ClassB/runtest.sh

Test Run Output

DMWG HTTPS transport not supported on the tested target

Final Result

INFO

Test Case # 6

Test Case Description

R2.8-2: For all resource endpoints, a service MUST return a wsa:ActionNotSupported fault (defined in WS-Addressing) if a requested action is not supported by the service for the specified resource

Test Details

Test Directory: ./tests/WS-Protocol/Action/InvalidAction
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/Action/InvalidAction/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 7

Test Case Description

R2.8-2: For all resource endpoints, a service MUST return a wsa:ActionNotSupported fault (defined in WS-Addressing) if a requested action is not supported by the service for the specified resource

Test Details

Test Directory: ./tests/WS-Protocol/Action/missingAction
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/Action/missingAction/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 8

Test Case Description

R2.8-5: All event deliveries MUST contain a unique action URI which identifies the type of the event delivery. For singleton deliveries with only one event per message (the delivery mode http://schemas.xmlsoap.org/ws/2004/08/eventing/DeliveryModes/Push ), the wsa:Action URI defines the event type. For other delivery modes, the Action varies, as described in section 6 of this specification

Test Details

Test Directory: ./tests/WS-Protocol/Action/validAction
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/Action/validAction/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 9

Test Case Description

R5-1-5: If a service is exposing enumeration, it MUST at least support the following messages wsen:enumerate, wsen:pull and wsen:release and their associated responses.

Test Details

Test Directory: ./tests/WS-Protocol/BasicEnumerate
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/BasicEnumerate/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 10

Test Case Description

R2.1.2-4: The Selector Name attribute MUST NOT be duplicated at the same level of nesting. The service SHOULD return a wsman:InvalidSelectors fault with a detail code of http://schemas.dmtf.org/wbem/wsman/1/wsman/faultDetail/DuplicateSelectors if this occurs.

Test Details

Test Directory

./tests/WS-Protocol/BasicGet

Basic Result Checking

Output doesn't conform with the Mandatory Requirements in the Specifications

Detailed Result Processing by using

./tests/WS-Protocol/BasicGet/runtest.sh

Test Run Output

sed: -e expression #1, char 3: unterminated `s' command
[Fatal Error] :-1:-1: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)
	at otm.xml.XMLGrepNode.main(XMLGrepNode.java:89)
[Fatal Error] :-1:-1: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)
	at otm.xml.XMLGrepNode.main(XMLGrepNode.java:89)
sed: -e expression #2, char 83: unterminated `s' command
Validation Against Schema Fail
[Fatal Error] :-1:-1: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:468)
	at otm.xml.XMLExtractNode.main(XMLExtractNode.java:122)
--------------- linked to ------------------
javax.xml.xpath.XPathExpressionException
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:473)
	at otm.xml.XMLExtractNode.main(XMLExtractNode.java:122)
Caused by: org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:468)
	... 1 more
wsa:Action checking Fail

Final Result

FAIL

Test Case # 11

Test Case Description

[CIM-Binding] R5.2-1: Instances of a specific class MUST accept an "All available Class" Resource URI

Test Details

Test Directory

./tests/WS-Protocol/EnumAllClassURI

Basic Result Checking

Output doesn't conform with the Mandatory Requirements in the Specifications

Detailed Result Processing by using

./tests/WS-Protocol/EnumAllClassURI/runtest.sh

Test Run Output

[Enumerate] wsa:Action checking Fail
[Enumerate] wsen:EnumerationContext is NULL
[PULL] wsa:Action checking Fail
[PULL] wsen:Items is NULL

Final Result

FAIL

Test Case # 12

Test Case Description

[CIM-Binding] R5.1-1: Instances of a specific class MUST be addressed using a ResourceURI identifying a specific class.

Test Details

Test Directory: ./tests/WS-Protocol/EnumClassURI
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/EnumClassURI/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 13

Test Case Description

R5.2.2-1: A conformant service MAY support the ability to return an estimate of the number of items in an enumeration sequence . If a service recieves an wsen:Enumerate or wsen:Pull message without the wsmanRequestTotalItemsCountRequest SOAP header, the service MUST NOT return the wsman.TotalItemsCountEstimate? SOAP header.

Test Details

Test Directory: ./tests/WS-Protocol/EnumCount
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/EnumCount/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 14

Test Case Description

R5.2.1-2: A conformant service MUST accept a wsen:Enumerate message with an Expires timeout or fault with wsman:UnsupportedFeature and a detail code of http://schemas.dmtf.org/wbem/wsman/1/wsman/faultDetail/ExpirationTime

R5.5-2

Test Details

Test Directory: ./tests/WS-Protocol/EnumExpiresTimeOut
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/EnumExpiresTimeOut/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 15

Test Case Description

R5.7-1: A service MAY optionally support the wsman:EnumerationMode modifier element with a value of EnumerateEPR, which returns only the EPRs of the objects as the result of the enumeration. R5.7-3: If a service does not support the wsman:EnumerationMode modifier, it MUST return a fault of wsman:UnsupportedFeature with a detail code of http://schemas.dmtf.org/wbem/wsman/1/wsman/faultDetail/EnumerationMode

Test Details

Test Directory

./tests/WS-Protocol/EnumModeEPR

Basic Result Checking

Output doesn't conform with the Mandatory Requirements in the Specifications

Detailed Result Processing by using

./tests/WS-Protocol/EnumModeEPR/runtest.sh

Test Run Output

[PULL] Validation Against Schema Fail

Final Result

FAIL

Test Case # 16

Test Case Description

R5.7-2: A service MAY optionally support the wsman:EnumerationMode modifier with the value of EnumerateObjectAndEPR. If present, the enumerated objects are wrapped in a wsman:Item which juxtaposes two XML representations: the payload representation followed by the associated wsa:EndpointReference. R5.7-3: If a service does not support the wsman:EnumerationMode modifier, it MUST return a fault of wsman:UnsupportedFeature with a detail code of http://schemas.dmtf.org/wbem/wsman/1/wsman/faultDetail/EnumerationMode

Test Details

Test Directory

./tests/WS-Protocol/EnumModeObjectEPR

Basic Result Checking

Output doesn't conform with the Mandatory Requirements in the Specifications

Detailed Result Processing by using

./tests/WS-Protocol/EnumModeObjectEPR/runtest.sh

Test Run Output

[Pull] Validation Against Schema Fail

Final Result

FAIL

Test Case # 17

Test Case Description

R5.2.3-2: A conformant service receiving an wsen:Enumerate message without the wsman:OptimizeEnumeration element MUST NOT return any enumeration items in the wsen:EnumerateResponse message and MUST return an wsen:EnumerationContext initialized to return the first items when the first wsen:Pull message is received R5.2.3-4: A conformant service that supports optimized enumeration and is responding with an wsen:EnumerateResponse message MUST include either or both the wsman:Items or wsman:EndOfSequence elements in the response as an indication to the client that the optimized enumeration request was understood and honored

Test Details

Test Directory: ./tests/WS-Protocol/EnumOptimize
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/EnumOptimize/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 18

Test Case Description

[CIM-Binding] R8.1-3: A service MAY optionally support the wsmb:PolymorphismMode modifier element with a value of None, which returns instances of the base class only.

[CIM-Binding]: R8.1-5: If a service does not support the requested polymorphism mode, it should return wsmb.:PolymorphismModeNotSupported fault

Test Details

Test Directory

./tests/WS-Protocol/EnumPolymorphismAllClass

Basic Result Checking

Output doesn't conform with the Mandatory Requirements in the Specifications

Detailed Result Processing by using

./tests/WS-Protocol/EnumPolymorphismAllClass/runtest.sh

Test Run Output

Polymorphism Mode Fail

Final Result

FAIL

Test Case # 19

Test Case Description

[CIM-Binding] R8.1-2: A service MAY optionally support the wsmb:PolymorphismMode modifier element with a value of ExcludeSubClassProperties?, which returns instances of the base and derived classes but represented using the base class's GED and XSD type. Properties unique to the derived class are not returned.

[CIM-Binding]: R8.1-5: If a service does not support the requested polymorphism mode, it should return wsmb.:PolymorphismModeNotSupported fault

Test Details

Test Directory

./tests/WS-Protocol/EnumPolymorphismExclude

Basic Result Checking

Output conforms with the Specifications

Detailed Result Processing by using

./tests/WS-Protocol/EnumPolymorphismExclude/runtest.sh

Test Run Output

CIM_System

Final Result

PASS

Test Case # 20

Test Case Description

[CIM-Binding] R8.1-4: A service MAY optionally support the wsmb:PolymorphismMode modifier element with a value of IncludeSubClassProperties?, which returns instances of the base and derived classes but represented using the actual class's GED and XSD type. This is same as not specifying the polymorphism mode

[CIM-Binding]: R8.1-5: If a service does not support the requested polymorphism mode, it should return wsmb.:PolymorphismModeNotSupported fault

Test Details

Test Directory

./tests/WS-Protocol/EnumPolymorphismInclude

Basic Result Checking

Output doesn't conform with the Mandatory Requirements in the Specifications

Detailed Result Processing by using

./tests/WS-Protocol/EnumPolymorphismInclude/runtest.sh

Test Run Output

[Fatal Error] runtest.xml:6:2: The content of elements must consist of well-formed character data or markup.
org.xml.sax.SAXParseException: The content of elements must consist of well-formed character data or markup.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)
	at otm.xml.XMLGrepNode.main(XMLGrepNode.java:89)
[Fatal Error] runtest.xml:6:2: The content of elements must consist of well-formed character data or markup.
org.xml.sax.SAXParseException: The content of elements must consist of well-formed character data or markup.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)
	at otm.xml.XMLGrepNode.main(XMLGrepNode.java:89)
[Fatal Error] runtest.xml:6:2: The content of elements must consist of well-formed character data or markup.
org.xml.sax.SAXParseException: The content of elements must consist of well-formed character data or markup.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)
	at otm.xml.XMLGrepNode.main(XMLGrepNode.java:89)
[Fatal Error] runtest.xml:6:2: The content of elements must consist of well-formed character data or markup.
org.xml.sax.SAXParseException: The content of elements must consist of well-formed character data or markup.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)
	at otm.xml.XMLGrepNode.main(XMLGrepNode.java:89)
sed: -e expression #1, char 36: unterminated `s' command
[Enumerate] Validation Against Schema Fail
[Fatal Error] :-1:-1: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:468)
	at otm.xml.XMLExtractNode.main(XMLExtractNode.java:122)
--------------- linked to ------------------
javax.xml.xpath.XPathExpressionException
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:473)
	at otm.xml.XMLExtractNode.main(XMLExtractNode.java:122)
Caused by: org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:468)
	... 1 more
Polymorphism Mode (IncludeSubClassProperties) Fail

Final Result

FAIL

Test Case # 21

Test Case Description

[CIM-Binding] R8.1-3: A service MAY optionally support the wsmb:PolymorphismMode modifier element with a value of None, which returns instances of the base class only.

[CIM-Binding]: R8.1-5: If a service does not support the requested polymorphism mode, it should return wsmb.:PolymorphismModeNotSupported fault

Test Details

Test Directory: ./tests/WS-Protocol/EnumPolymorphismNone
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/EnumPolymorphismNone/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 22

Test Case Description

R11.2-1: A conformant service MUSt use the fault encoding format and normative constraints defined below for faults in the WS_Management spaces of any of its dependent specifications

Test Details

Test Directory: ./tests/WS-Protocol/FaultEncoding
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/FaultEncoding/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 23

Test Case Description

R2.9-1: R2.9-2:

Test Details

Test Directory: ./tests/WS-Protocol/From/mustUnderstandFalse
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/From/mustUnderstandFalse/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 24

Test Case Description

R2.1.1-1: The format of the wsman:ResourceURI is unconstrained provided that it meets RFC 3986 requirements.

Test Details

Test Directory: ./tests/WS-Protocol/From/mustUnderstandTrue
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/From/mustUnderstandTrue/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 25

Test Case Description

R6-4: Services supporting Get and using the WS-Management Default Addressing

Model SHOULD support access using the class-specific ResourceURI corresponding to the base class and the selectors of an instance of the derived class.

Test Details

Test Directory

./tests/WS-Protocol/GetBaseInstance

Basic Result Checking

Output conforms with the Specifications

Detailed Result Processing by using

./tests/WS-Protocol/GetBaseInstance/runtest.sh

Test Run Output

sed: -e expression #1, char 3: unterminated `s' command
[Fatal Error] :-1:-1: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)
	at otm.xml.XMLGrepNode.main(XMLGrepNode.java:89)
[Fatal Error] :-1:-1: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)
	at otm.xml.XMLGrepNode.main(XMLGrepNode.java:89)
sed: -e expression #2, char 83: unterminated `s' command
Validation Against Schema Fail
[Fatal Error] :-1:-1: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:468)
	at otm.xml.XMLExtractNode.main(XMLExtractNode.java:122)
--------------- linked to ------------------
javax.xml.xpath.XPathExpressionException
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:473)
	at otm.xml.XMLExtractNode.main(XMLExtractNode.java:122)
Caused by: org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:468)
	... 1 more
Fail: Derived Class Selectors Cannot Access Base Class
[Fatal Error] :-1:-1: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:468)
	at otm.xml.XMLExtractNode.main(XMLExtractNode.java:122)
--------------- linked to ------------------
javax.xml.xpath.XPathExpressionException
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:473)
	at otm.xml.XMLExtractNode.main(XMLExtractNode.java:122)
Caused by: org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:468)
	... 1 more
 Response does not matches BaseClassName

Final Result

WARN

Test Case # 26

Test Case Description

[CIM-BINDING] R6-3: Services supporting Get and using the WS-Management Default Addressing Model MUST support access using the class-specific ResourceURI corresponding to the final class (not a base class) and the selectors of the given instance.

Test Details

Test Directory

./tests/WS-Protocol/GetDerivedInstance

Basic Result Checking

Output doesn't conform with the Mandatory Requirements in the Specifications

Detailed Result Processing by using

./tests/WS-Protocol/GetDerivedInstance/runtest.sh

Test Run Output

sed: -e expression #1, char 3: unterminated `s' command
[Fatal Error] :-1:-1: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)
	at otm.xml.XMLGrepNode.main(XMLGrepNode.java:89)
[Fatal Error] :-1:-1: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)
	at otm.xml.XMLGrepNode.main(XMLGrepNode.java:89)
sed: -e expression #2, char 83: unterminated `s' command
Validation Against Schema Fail
[Fatal Error] :-1:-1: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:468)
	at otm.xml.XMLExtractNode.main(XMLExtractNode.java:122)
--------------- linked to ------------------
javax.xml.xpath.XPathExpressionException
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:473)
	at otm.xml.XMLExtractNode.main(XMLExtractNode.java:122)
Caused by: org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:468)
	... 1 more
Fail: Derived Class Selectors Cannot Access Base Class
[Fatal Error] :-1:-1: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:468)
	at otm.xml.XMLExtractNode.main(XMLExtractNode.java:122)
--------------- linked to ------------------
javax.xml.xpath.XPathExpressionException
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:473)
	at otm.xml.XMLExtractNode.main(XMLExtractNode.java:122)
Caused by: org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:468)
	... 1 more
 Response does not matches BaseClassName

Final Result

FAIL

Test Case # 27

Test Case Description

Test Details

Test Directory

./tests/WS-Protocol/GetFragment

Basic Result Checking

Output doesn't conform with the Mandatory Requirements in the Specifications

Detailed Result Processing by using

./tests/WS-Protocol/GetFragment/runtest.sh

Test Run Output

sed: -e expression #1, char 3: unterminated `s' command
[Fatal Error] :-1:-1: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)
	at otm.xml.XMLGrepNode.main(XMLGrepNode.java:89)
[Fatal Error] :-1:-1: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)
	at otm.xml.XMLGrepNode.main(XMLGrepNode.java:89)
sed: -e expression #2, char 83: unterminated `s' command
Validation Against Schema Fail
[Fatal Error] :-1:-1: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:468)
	at otm.xml.XMLExtractNode.main(XMLExtractNode.java:122)
--------------- linked to ------------------
javax.xml.xpath.XPathExpressionException
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:473)
	at otm.xml.XMLExtractNode.main(XMLExtractNode.java:122)
Caused by: org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:468)
	... 1 more
Fragment Level Get Operation Failed

Final Result

FAIL

Test Case # 28

Test Case Description

R3.3-1: If mustUnderstand is omitted or set to false, the sservice should utilize this value when composing the response mesage and adjust any localizable values accordingly. This is RECOMMENDED usuage for most cases. The locale is treated as a 'hint' in this case.

Test Details

Test Directory

./tests/WS-Protocol/Locale/mustUnderstandFalse

Basic Result Checking

Output conforms with the Specifications

Detailed Result Processing by using

./tests/WS-Protocol/Locale/mustUnderstandFalse/runtest.sh

Test Run Output

c3509846-2ad2-1ad2-8043-a052ae761600

Final Result

PASS

Test Case # 29

Test Case Description

Test Details

Test Directory: ./tests/WS-Protocol/Locale/mustUnderstandTrue
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/Locale/mustUnderstandTrue/runtest.sh
Test Run Output
Final Result: INFO

Test Case # 30

Test Case Description

R3.2.2: If mustUnderstand is set to true, the service MUST comply with the request. If the response would exceed the maximum size, then a wsman:EncodingLimit fault SHOULD be returned.

Test Details

Test Directory: ./tests/WS-Protocol/MaxEnvelope
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/MaxEnvelope/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 31

Test Case Description

R2.7-2: The MessageID SHOULD be generated according to any algorithm whichensures that no two MessageIDs will repeat. Since the value is treated as case-sensitive (R2.7-1), confusion can arise if the same value is reused differing only in case, so the service MUST NOT create or employ MessageID values which differ only in case. For any message transmitted by the service, the MessageID MUST NOT be reused

Test Details

Test Directory: ./tests/WS-Protocol/MsgIDRelatesTo/duplicateMsgId
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/MsgIDRelatesTo/duplicateMsgId/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 32

Test Case Description

R2.7-4: If the message ID is not parsable or is missing a wsa:InvalidMessageInformationHeader fault should be returned

Test Details

Test Directory

./tests/WS-Protocol/MsgIDRelatesTo/invalidMsgId

Basic Result Checking

Output doesn't conform with the Mandatory Requirements in the Specifications

Detailed Result Processing by using

./tests/WS-Protocol/MsgIDRelatesTo/invalidMsgId/runtest.sh

Test Run Output

wsa:Action checking Fail
s:Code checking Fail
s:Subcode checking Fail

Final Result

FAIL

Test Case # 33

Test Case Description

R2.7-4: If the message ID is not parsable or is missing a wsa:InvalidMessageInformationHeader fault should be returned

Test Details

Test Directory: ./tests/WS-Protocol/MsgIDRelatesTo/missingMsgId
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/MsgIDRelatesTo/missingMsgId/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 34

Test Case Description

R2.7-3The RelatesTo? MUST be present in all response messages and faults, MUST contain the MessageID of the associated request message, and MUST match the original in case, being treated as a URI value and not as binary GUID value.

Test Details

Test Directory

./tests/WS-Protocol/MsgIDRelatesTo/MsgIdEqRelatesTo

Basic Result Checking

Output conforms with the Specifications

Detailed Result Processing by using

./tests/WS-Protocol/MsgIDRelatesTo/MsgIdEqRelatesTo/runtest.sh

Test Run Output

c54d7638-2ad2-1ad2-804d-a052ae761600

Final Result

PASS

Test Case # 35

Test Case Description

R3.1-3: If the service does not support user defined timeouts a wsman:UnsupportedFeature fault should be returned with a detail code of http://schemas.dmtf.org/wsman/1wsman/faultDetails/OperationTimeout

Test Details

Test Directory

./tests/WS-Protocol/OperationTimeout/invalidValue

Basic Result Checking

Output conforms with the Specifications

Detailed Result Processing by using

./tests/WS-Protocol/OperationTimeout/invalidValue/runtest.sh

Test Run Output

wsman:FaultDetail checking Fail

Final Result

WARN

Test Case # 36

Test Case Description

R3.1-2: Service should immediately issue wsman:TimedOut fault if the countdown time is exceeded and the operation is not yet complete. If the OperationTimeout? value is not valid, then the wsman:InvalidHeader fault should be generated with the detail code of http://schemas.dmtf.org/wbem/wsman/1/wsman/faultDetail/InvalidTimeout

Test Details

Test Directory: ./tests/WS-Protocol/OperationTimeout/validValue
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/OperationTimeout/validValue/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 37

Test Case Description

R3.4-3: If the mustUnderstand attribute is omitted from the OptionSet? block, then the service MAY ignore the entire wsman:OptionSet block. If it is present and the service does not support wsman:OptionSet, the service MUST return a s:NotUnderstood fault R3.4-5:Any number of individual Option elements may appear under the wsman:OptionSet wrapper. Option names MAY be repeated if appropriate. The content MUST be a simple string (xs:string). This specification places no restrictions on whether the names or values are to be treated in a case sensitive or case-insensitive manner. Case usage MUST be retained because the OptionSet? and its contents are propagated through SOAP intermediaries. IR3.4-6: ndividual option values may be advisory or may be required by the client. The service must observe and execute any option marked with the MustComply? attribute set to "true", or return a wsman:InvalidOptions fault with a detail code of http://schemas.dmtf.org/wbem/wsman/1/wsman/faultDetail/NotSupported. Any option not marked with this attribute (or if the attribute is set to "false") is advisory to the service and MAY be ignored by the service. If any option is marked with MustComply? set to "true", then mustUnderstand MUST be used on the entire wsman:OptionSet block.

Test Details

Test Directory: ./tests/WS-Protocol/OptionSet/mustUnderstandFalse
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/OptionSet/mustUnderstandFalse/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 38

Test Case Description

Test Details

Test Directory: ./tests/WS-Protocol/OptionSet/mustUnderstandTrue
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/OptionSet/mustUnderstandTrue/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 39

Test Case Description

R5.2.3-5: R5.2.3-4: R5.5-1:

Test Details

Test Directory: ./tests/WS-Protocol/PullEOSRelease
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/PullEOSRelease/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 40

Test Case Description

This will test Pull using invalid Enum Context

Test Details

Test Directory: ./tests/WS-Protocol/PullInvalidEnumContext
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/PullInvalidEnumContext/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 41

Test Case Description

R5.4-6: The service MUST accept a wsen:Pull message with an endpoint reference identical to that specified for the original wsen:Enumeration. A wsa:MessageInformationHeaderRequired fault should be returned if the EPR is missing or different.

R5.4-12: The wsen:EnumerationContext MUST be present in all wsen:Pull request, even if the service uses a constant value for the lifetime of the enumeration sequence. This is mandated by WS-Enumeration and repeated here for clarification.

Test Details

Test Directory: ./tests/WS-Protocol/PullInvalidEPR
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/PullInvalidEPR/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 42

Test Case Description

R5.4-2:If a service is exposing enumeration and supports wsen:Pull with the wsen:MaxCharacters element, and a single response element would cause the limit to be exceeded, the service MAY return the single element in violation of the hint. However, the service MUST NOT violate wsman:MaxEnvelopeSize in any case

R5.4-3: If a wsen:PullResponse would violate the wsman:MaxEnvelopeSize request, the service MUST return a wsman:EncodingLimit fault with a detail code of one of the following

" http://schemas.dmtf.org/wbem/wsman/1/wsman/faultDefault/MaxEnvelopeSize if the client's requested maximum would have been exceeded " http://schemas.dmtf.org/wbem/wsman/1/wsman/faultDefault/ServiceEnvelopeLimit if the service's internal limit was exceeded

Test Details

Test Directory: ./tests/WS-Protocol/PullMaxCharGtMaxEnv
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/PullMaxCharGtMaxEnv/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 43

Test Case Description

R5.4-3: If a wsen:PullResponse would violate the wsman:MaxEnvelopeSize request, the service MUST return a wsman:EncodingLimit fault with a detail code of one of the following

Test Details

Test Directory: ./tests/WS-Protocol/PullMaxCharLtMaxEnv
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/PullMaxCharLtMaxEnv/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 44

Test Case Description

Test Details

Test Directory: ./tests/WS-Protocol/PullmissingEnumContext
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/PullmissingEnumContext/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 45

Test Case Description

This will test Pull using invalid Enum Context

Test Details

Test Directory: ./tests/WS-Protocol/ReleaseInvalidEnumContext
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/ReleaseInvalidEnumContext/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 46

Test Case Description

R5.5-3: The service MUST accept a wsen:Release message with an endpoint reference identical to that specified for the original wsen:Enumeration. A wsa:MessageInformationHeaderRequired fault should be returned if the EPR is missing or different.

Test Details

Test Directory: ./tests/WS-Protocol/ReleaseInvalidEPR
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/ReleaseInvalidEPR/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 47

Test Case Description

Test Details

Test Directory: ./tests/WS-Protocol/ReleaseMissingEnumContext
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/ReleaseMissingEnumContext/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 48

Test Case Description

R5.5-2

Test Details

Test Directory: ./tests/WS-Protocol/ReleaseTimeOut
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/ReleaseTimeOut/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 49

Test Case Description

R2.5-1: A wsa:ReplyTo header MUST be present in all request messages when a reply is required. This MUST either be a valid address for a new connection using any transport supported by the service, or the URI http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous (see WS-Addressing), which indicates that the reply is to be delivered over the same connection on which the request arrived. If the wsa:ReplyTo is missing, a wsa:MessageInformationHeaderRequired fault is returned.

Test Details

Test Directory: ./tests/WS-Protocol/ReplyTo/missingReplyTo
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/ReplyTo/missingReplyTo/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 50

Test Case Description

R2.5-4:Service MUST fully duplicate the entire wsa:Address of the wsa:ReplyTo element in the wsa:To of the reply, even if some of the information is not understood by the service

Test Details

Test Directory: ./tests/WS-Protocol/ReplyTo/ReplyToEqWsaTo
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/ReplyTo/ReplyToEqWsaTo/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 51

Test Case Description

R2.5-5: Any reference parameters supplied in the wsa:ReplyTo address MUST be included in the actual response message as top-level headers as specified in WS-Addressing unless the response is a fault. If the response is a fault, then the service SHOULD include the reference parameters but MAY omit these values if the resulting message size would exceed encoding limits

Test Details

Test Directory: ./tests/WS-Protocol/ReplyTo/ReplyToRefParam
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/ReplyTo/ReplyToRefParam/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 52

Test Case Description

[CIM-Binding] R5.3.1: Services offering more than one CIM NameSpace? MUST use the selector cimnamespace to locate resource(s) within CIM Namespace

[CIM-Binding] R5.3.2: Service MUST not fault if the cimnamespace selector is absent and instead MUSt locate the resource within the default namespace

Test Details

Test Directory

./tests/WS-Protocol/Selector/cimnamespace

Basic Result Checking

Output conforms with the Specifications

Detailed Result Processing by using

./tests/WS-Protocol/Selector/cimnamespace/runtest.sh

Test Run Output

ce9a6deb-2ad2-1ad2-807e-a052ae761600

Final Result

PASS

Test Case # 53

Test Case Description

Test Details

Test Directory

./tests/WS-Protocol/Selector/duplicateSelector

Basic Result Checking

Output doesn't conform with the Mandatory Requirements in the Specifications

Detailed Result Processing by using

./tests/WS-Protocol/Selector/duplicateSelector/runtest.sh

Test Run Output

sed: -e expression #1, char 3: unterminated `s' command
[Fatal Error] :-1:-1: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)
	at otm.xml.XMLGrepNode.main(XMLGrepNode.java:89)
[Fatal Error] :-1:-1: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:172)
	at otm.xml.XMLGrepNode.main(XMLGrepNode.java:89)
sed: -e expression #2, char 83: unterminated `s' command
Validation Against Schema Fail
[Fatal Error] :-1:-1: Premature end of file.
org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:468)
	at otm.xml.XMLExtractNode.main(XMLExtractNode.java:122)
--------------- linked to ------------------
javax.xml.xpath.XPathExpressionException
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:473)
	at otm.xml.XMLExtractNode.main(XMLExtractNode.java:122)
Caused by: org.xml.sax.SAXParseException: Premature end of file.
	at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:264)
	at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
	at com.sun.org.apache.xpath.internal.jaxp.XPathImpl.evaluate(XPathImpl.java:468)
	... 1 more
wsa:Action checking Fail

Final Result

FAIL

Test Case # 54

Test Case Description

R2.1.2-3: A service using the WS-Management default addressing model MUST examine all Selectors in the message and process them as if they were logically ANDed. If the set of Selec is incorrect for the targeted resource instance, then a wsman:InvalidSelectors fault SHOULD be returned to the client with the following detail codes: d) d) http://schemas.dmtf.org/wbem/wsman/1/wsman/faultDetail/UnexpectedSelectors if the Name

is not a recognized Selector name.

Test Details

Test Directory

./tests/WS-Protocol/Selector/invalidName

Basic Result Checking

Output doesn't conform with the Mandatory Requirements in the Specifications

Detailed Result Processing by using

./tests/WS-Protocol/Selector/invalidName/runtest.sh

Test Run Output

wsa:Action checking Fail

Final Result

FAIL

Test Case # 55

Test Case Description

a) http://schemas.dmtf.org/wbem/wsman/1/wsman/faultDetail/InsufficientSelectors if Select

are missing

Test Details

Test Directory: ./tests/WS-Protocol/Selector/missingSelector
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/Selector/missingSelector/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 56

Test Case Description

R2.1.1-8: If the wsman:Resource URI is invalid, the service MUST issue a wsa:DestinationUnreachable fault with a detail code of http://schemas.dmtf.org/wbem/wsman/1/wsman/fault/faultDetail/InvalidResourceURI

Test Details

Test Directory: ./tests/WS-Protocol/URI/invalidResourceURI
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/URI/invalidResourceURI/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 57

Test Case Description

R2.1.1-5: If the wsman:Resource URI is missing, the service MUST issue a wsa:DestinationUnreachable fault with a detail code of http://schemas.dmtf.org/wbem/wsman/1/wsman/fault/faultDetail/InvalidResourceURI

Test Details

Test Directory: ./tests/WS-Protocol/URI/missingResourceURI
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/URI/missingResourceURI/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 58

Test Case Description

R2.1.1-1: The format of the wsman:ResourceURI is unconstrained provided that it meets RFC 3986 requirements.

Test Details

Test Directory

./tests/WS-Protocol/URI/validResourceURI

Basic Result Checking

Output conforms with the Specifications

Detailed Result Processing by using

./tests/WS-Protocol/URI/validResourceURI/runtest.sh

Test Run Output

d20ee574-2ad2-1ad2-8090-a052ae761600

Final Result

PASS

Test Case # 59

Test Case Description

R2.4-2: The service SHOULD issue faults when failing to evaluate the address of the resource in the following situations:

If the resource is offline, a wsa:EndpointUnavailable fault is returned with a detail code of http://schemas.dmtf.org/wbem/wsman/1/wsman/faultDetail/ResourceOffline Code- s:Reciever

o If the resource cannot be located ("not found"), a wsa:DestinationUnreachable fault is returned. Code s:sender o If the resource is valid, but internal errors occur, a wsman:InternalError fault is returned. Code s:Receiver

o If the resource cannot be accessed for security reasons, a wsman:AccessDenied fault is returned Code - s:sender

R2.3-1 A conformant service MUST process any of the above elements identically whether mustUnderstand="true" is present or not

Test Details

Test Directory: ./tests/WS-Protocol/WsaTo/missingWsaTo
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/WsaTo/missingWsaTo/runtest.sh
Test Run Output
Final Result: PASS

Test Case # 60

Test Case Description

R2.4-2: The service SHOULD issue faults when failing to evaluate the address of the resource in the following situations: If the resource is offline, a wsa:EndpointUnavailable fault is returned with a detail code of http://schemas.dmtf.org/wbem/wsman/1/wsman/faultDetail/ResourceOffline Code- s:Reciever

o If the resource cannot be accessed for security reasons, a wsman:AccessDenied fault is returned Code - s:sender

R2.3-1: A conformant service MUST process any of the above elements identically whether mustUnderstand="true" is present or not

Test Details

Test Directory

./tests/WS-Protocol/WsaTo/mustUnderstandTrue/invalidWsaTo

Basic Result Checking

Output doesn't conform with the Mandatory Requirements in the Specifications

Detailed Result Processing by using

./tests/WS-Protocol/WsaTo/mustUnderstandTrue/invalidWsaTo/runtest.sh

Test Run Output

wsa:Action checking Fail
s:Code checking Fail
s:Subcode checking Fail

Final Result

FAIL

Test Case # 61

Test Case Description

R2.3-1: A conformant service MUST process any of the above elements identically whether mustUnderstand="true" is present or no R2.4-2:The wsa:To header MUST be present in all messages, whether requests, responses, or events, and SHOULD reflect a valid URI. In the absence of other requirements, it is RECOMMENDED that the network address be suffixed by the token sequence /wsman: (1) <wsa:To> http://123.15.166.67/wsman </wsa:To>

Test Details

Test Directory

./tests/WS-Protocol/WsaTo/mustUnderstandTrue/validWsaTo

Basic Result Checking

Output conforms with the Specifications

Detailed Result Processing by using

./tests/WS-Protocol/WsaTo/mustUnderstandTrue/validWsaTo/runtest.sh

Test Run Output

d2f1a742-2ad2-1ad2-8095-a052ae761600

Final Result

PASS

Test Case # 62

Test Case Description

R2.4-1:The wsa:To header MUST be present in all messages, whether requests, responses, or events, and SHOULD reflect a valid URI. In the absence of other requirements, it is RECOMMENDED that the network address be suffixed by the token sequence /wsman: (1) <wsa:To> http://123.15.166.67/wsman </wsa:To>

R2.3-1: A conformant service MUST process any of the above elements identically whether mustUnderstand="true" is present or not

Test Details

Test Directory: ./tests/WS-Protocol/WsaTo/validWsaTo
Basic Result Checking: Output conforms with the Specifications
Detailed Result Processing by using: ./tests/WS-Protocol/WsaTo/validWsaTo/runtest.sh
Test Run Output
Final Result: PASS

Download in other formats:

Plain Text