JSON Schema for 2.0 to validate method parameter use two oneOf one inside each other.
This leads to an unreadable error message if an error occurs inside a parameter.
And it's true for all tools which are use official JSON Schema for validation.
I used Swagger Editor as example of such behaviour:

I think it's very important issue since it can push away newcomers who just want to try OpenAPI 2.0 for the first time.
I have a solution for this problem which requires making few changes in current JSON Schema.
As a nice bonus, it reduces duplication in parameters definitions and overall size of JSON Schema.
But before submitting such changes I want to test them thoroughly.
That is why I want to finish my work on unit test.