Submit and vote on feature ideas.

Welcome to the new Parasoft forums! We hope you will enjoy the site and try out some of the new features, like sharing an idea you may have for one of our products or following a category.

Unknown Service in SOAtest report for tests created from swagger file

Options
kseniia
kseniia Posts: 5 ✭
edited December 2023 in SOAtest

I'm seeing "Unknown Service" thing in my SOAtest report for all the tests I made from my Swagger .yaml file. It's showing two things under 'coverable resources" section of the report - my .yml file and "Unknown Service." But the coverage is only happening for the file. I'm using the default User-defined example configuration with "Calculate coverage against service definitions referenced by tests" turned on.

Note: the "Unknown Service" has the exact same list of resources listed as my .yml file, but without any parameters.
Example:
file:///C:testing.yaml has "/addPinToGroup/{key}/{product}/{pin}"
the unknown service has "https://baseurl.com/addPinToGroup///"

Any ideas on where it's picking up this "unknown service," and how can I make it go away from the report?

Answers

  • benken_parasoft
    benken_parasoft Posts: 1,235 ✭✭✭
    edited December 2023
    Options

    Are you sending requests to "https://baseurl.com/addPinToGroup///"? Make sure you define non-empty values for those path parameters. Then the request should match what is defined in your OpenAPI/Swagger definition instead of "Unknown Service".

Categories