|
Post by dkodihalli on Jul 19, 2023 7:22:24 GMT
Are these existing tools to achieve all of the following (end-to-end tree and property value GET validation):
1. Generate a "source-of-truth" mockup from a live service. I believe this can be done via the mockup-creator (assuming a fully functional/max config/bug-free live service).
2. Checking conformance of the live service against schemas - service-validator can be used.
3. Making sure the live service has all expected URIs and properties, and no unexpected URIs and properties. Can this be a tree comparison - Redfish tree from live service and the tree generated from 1) above?
4. Property value validation (GETs) - once we done 3, we know the tree is as expected. Can interop validator be used for validation of the values of properties? Does it handle a case where the same property's value may have different allowed values/ranges for two different URIs of the same type (for example, Chassis_CPU vs Chassis_Baseboard)? I've seen in other threads that POST/PATCH is still a pending item with the interop validator.
Is the above a possible recipe or is there another recommended way/other tools?
|
|
|
Post by mraineri on Jul 19, 2023 12:38:48 GMT
1) Yes, you can do this to make a static mockup for testing. This isn't necessary since each tool also operates on live services.
2) Yes, the service validator is used for this.
3) The interop validator could be used for this. In your profile, you specify which URIs and properties are mandatory. However, profiles do not disallow URIs or properties; one of the tenets of Redfish is that additional properties and URIs do not hurt users, and implementers are free to go above and beyond baseline requirements. However, I suspect you're thinking about this from the perspective of an implementer verifying their service is built the way it's specified; you can certainly do tree comparisons to test for this.
4) Yes, you can use the interop validator for this. The "conditional requirements" and "use cases" constructs in the profile can specify those sorts of variations.
In terms of payload validation, you've covered everything that comes to my mind. I can't think of other tools or tests.
|
|