[//]: # (
. This repository's issues are reserved for feature requests and bug reports.
.
. Make sure you have a clear name for your issue. The name should start with a capital
. letter and no dot is required in the end of the sentence. An example of good issue names:
.
. - Bad perfomance with a large specification
. - Support OAS3
)
I'm submitting a ...
[ ] bug report
[x] feature request
What is the current behavior?
Integrate pactum tests to generate the Swagger coverage report.
I have E2E tests written in Pactum, and want to generate coverage report for APIs using the Open API specification.
Could you please help me in in generating the coverage report for these tests.
[//]: # ( . This repository's issues are reserved for feature requests and bug reports. . . Make sure you have a clear name for your issue. The name should start with a capital . letter and no dot is required in the end of the sentence. An example of good issue names: . . - Bad perfomance with a large specification . - Support OAS3 )
I'm submitting a ...
What is the current behavior?
Integrate pactum tests to generate the Swagger coverage report.
I have E2E tests written in Pactum, and want to generate coverage report for APIs using the Open API specification.
Could you please help me in in generating the coverage report for these tests.
Could you please help me understanding how to save information of calls in swagger format?
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 reports for the E2E tests written in pactum js.
Other information
[//]: # ( . e.g. detailed explanation, stacktraces, related issues, suggestions . how to fix, links for us to have more context )