Paramteres in the enpoints are not able to covered

[karishma191119]

I'm submitting a ...

• [x] bug report

• [ ] feature request

  What is the current behavior? paramters in the url or the endpoints are not covering,it is showing null is not empty

if the current behavior is a bug, please provide steps to reproduce, broken swagger specification and swagger-coverage-output:

What is the expected behavior?

What is the motivation / use case for changing the behavior? Generate coverage report for parameters

[viclovsky]

Hi, @karishma191119 Sounds like you have specification with broken paths in $ref I’ll fix $ref in the nearest future. To overcame the issue you should make workaround: list all files with specification in the only one file.

[viclovsky]

Ok, got it. Sounds like you should add special option : https://github.com/viclovsky/swagger-coverage#specification-parser-configuration

"parseOptions": {
  "resolve": true
}

It your $ref has right paths => all should work fine. In nearest release, I’ll add switching on $refs by default.

[karishma191119]

Ok, got it. Sounds like you should add special option : https://github.com/viclovsky/swagger-coverage#specification-parser-configuration

"parseOptions": {
  "resolve": true
}

It your $ref has right paths => all should work fine. In nearest release, I’ll add switching on $refs by default.

[karishma191119]

Ok, got it. Sounds like you should add special option : https://github.com/viclovsky/swagger-coverage#specification-parser-configuration

"parseOptions": {
  "resolve": true
}

It your $ref has right paths => all should work fine. In nearest release, I’ll add switching on $refs by default.

Thank you for responding @viclovsky, I tried of this solution in many ways to implement,but it dosent work,Can you please allobrate how to pass this "parseOptions parameter"...It will help us if you provide detail solution and also hope that you will add this $ref in this tool