While following the instructions in Specmatic Contract Testing Docs, I encountered an issue when running:
specmatic test employees.yaml --testBaseURL https://my-json-server.typicode.com
The command failed with the error:
Endpoints API and SwaggerUI URL were not exposed by the application, so cannot calculate actual coverage.
However, when I used the revised base URL:
specmatic test employees.yaml --testBaseURL https://my-json-server.typicode.com/specmatic/specmatic-documentation-examples
the operation succeeded.
A similar discrepancy occurs in strict mode.
This fails:
specmatic test --testBaseURL https://my-json-server.typicode.com --strict employees.yaml
This succeeds:
specmatic test --testBaseURL https://my-json-server.typicode.com/specmatic/specmatic-documentation-examples --strict employees.yaml
Additionally, the response object for POST /specmatic/specmatic/employees contains an unexpected attribute specmaticId, which is not defined in employees.yaml.
While following the instructions in Specmatic Contract Testing Docs, I encountered an issue when running:
specmatic test employees.yaml --testBaseURL https://my-json-server.typicode.comThe command failed with the error:
Endpoints API and SwaggerUI URL were not exposed by the application, so cannot calculate actual coverage.However, when I used the revised base URL:
specmatic test employees.yaml --testBaseURL https://my-json-server.typicode.com/specmatic/specmatic-documentation-examplesthe operation succeeded.
A similar discrepancy occurs in strict mode.
This fails:
specmatic test --testBaseURL https://my-json-server.typicode.com --strict employees.yamlThis succeeds:
specmatic test --testBaseURL https://my-json-server.typicode.com/specmatic/specmatic-documentation-examples --strict employees.yamlAdditionally, the response object for
POST /specmatic/specmatic/employeescontains an unexpected attributespecmaticId, which is not defined inemployees.yaml.