How to handle warnings in OTST tests

[samigamer1999]

Description

Suppose a sandbox env doesn't support (yet) some optional OSDM fields passed in a request. There are 2 possibilities :

• The endpoint refuses the request with a 422 status code for example
• Accept the request but doesn't take the optional non-supported fields into account, and returns the result with warnings/problems (with a PARTIAL_SUCCESS code) for the non-accounted for fields.

What would be the best approach in this case for OTST ?

In both cases, this is a bit problematic in OTST tests. It seems to me that the second approach is more favorable, however, we would need to overlay the OTST tests to check warnings for every request, especially that warnings/problems are environment specific and tests would have to adapt to all supported environment.