added fix for issue 959

[r-sreesaran]

fix for issue #959

[ymohdriz]

Hi @r-sreesaran,

Please find below my suggestions.

1. It's always better to assert the exact message instead of messages size.
2. Add a test case that no warning should throw when parameter with same name and location in both the operation and path level.
3. Add a test case that duplicate parameter should check in operation level or path level.
4. We have to handle the reference parameter (both internal and external). Please add a TC to cover this scenario.
5. Warning added in getParameters() is not required. Warning added in getParametersList() is enough.

Thanks,
Mohammed Rizwan

[gracekarina]

Hi, thanks for this PR. I suggest to divide the test in two, instead of evaluating two different specs in one test. @r-sreesaran