Releases: DMTF/Redfish-Service-Conformance-Check
Releases · DMTF/Redfish-Service-Conformance-Check
1.1.2
03 Aug 17:59
Compare
Sorry, something went wrong.
No results found
Changes since last release:
[1.1.2] - 2018-08-03
Added checking for presence of an action before trying to test the action
1.1.1
16 Jul 12:22
Compare
Sorry, something went wrong.
No results found
Changes since last release:
[1.1.1] - 2018-07-16
Added caching mechanism to allow for reuse of responses in different tests
Reduced the sample size of URIs performed in each test to have the tool run to completion in a shorter amount of time
1.1.0
06 Jul 12:27
Compare
Sorry, something went wrong.
No results found
Changes since last release:
[1.1.0] - 2018-07-06
Added change to use a higher level of TLS
Changed default password used for test cases
Fixes to tests that check for resource changes after a PATCH
1.0.9
01 Jun 12:58
Compare
Sorry, something went wrong.
No results found
Changes since last release:
[1.0.9] - 2018-06-01
Updated schema bundle to use the 2018.1 release
1.0.8
04 May 12:26
Compare
Sorry, something went wrong.
No results found
Changes since last release:
[1.0.8] - 2018-05-04
Fixed schema download to use a zip file instead of downloading them individually
1.0.7
27 Apr 12:13
Compare
Sorry, something went wrong.
No results found
Changes since last release:
[1.0.7] - 2018-04-27
Made fix to allow for the Oem property to be inside of Actions
1.0.6
13 Apr 12:52
Compare
Sorry, something went wrong.
No results found
Changes since last release:
[1.0.6] - 2018-04-13
Added type checking of responses to ensure they're JSON objects
1.0.5
16 Mar 12:21
Compare
Sorry, something went wrong.
No results found
Changes since last release:
[1.0.5] - 2018-03-16
Fixed test cases that validated redirect handling
Corrected primitive type checking done in schemas
1.0.4
09 Mar 13:04
Compare
Sorry, something went wrong.
No results found
Changes since last release:
[1.0.4] - 2018-03-09
Fixed bug where it was not able to handle multiple properties of the same name in different objects in the same payload
Fixed bug where the members of a collection were not being handled properly when validating the usage of @odata.nextLink
Fixed test cases where it was validating the response of an Action, but not handling corner cases appropriately
Corrected check for the HEAD method; this is not required to be supported on a service
Corrected Allow header check; this is only mandatory when the HTTP status code is 405
1.0.3
02 Mar 18:49
Compare
Sorry, something went wrong.
No results found
Changes since last release:
[1.0.3] - 2018-03-02
Corrected the enforcement of the Allow header on GET requests
Hardened the validation of error responses
Added initial test cases for validating normative language in the AccountService schema