API Validation: Post /shells 3rd API Call

[juileetikekar]

In case of API validation "Asset Administration Shell Repository API", the test-engine triggers POST "/shells" API call consisting of request body attached in the end. The request body consists of "EmbeddedDataSpecifications" as below:

The serialization of DataSpecification is treated as an array instead of an object and it consist of null content which unexpected. Even though above the serialization of "dataSpecification" is invalid, the test-engine expects 2xx (success), instead of 400 (BadRequest) from the server.

RequestBody:
request_body.json

Screenshot of test-engine result for this API validation: