Abstract: A testing method accesses tracing data comprising a plurality of tracing records corresponding to a plurality of test cases executed on a target system. The target system includes a plurality of microservices configured in accordance with a REST API. A dynamic test analyzer accesses the tracing data and imports a definition of the REST API. The analyzer checks each tracing record for consistency with the API definition. Based on this checking of the tracing records, one or more coverage metrics may be calculated. If any one or more of the one or more coverage metrics fails to exceed a threshold coverage, a testing action may be required. In some cases, the testing action may be selected from either seeking additional coverage of the APIs included in the target system or seeking additional test result coverage.

Abstract: Disclosed subject matter includes a testing method that accesses tracing data, comprising a plurality of tracing records corresponding to a plurality of test cases executed on a target system. The target system includes a plurality of microservices configured in accordance with a REST API. A dynamic test analyzer accesses the tracing data and imports a definition of the REST API. The analyzer checks each tracing record for consistency with the API definition. Based on this checking of the tracing records, one or more coverage metrics may be calculated. If any one or more of the coverage metrics fails to exceed a threshold coverage, a testing action may be required. In some cases, the testing action may be selected from either seeking additional coverage of the APIs included in the target system or seeking additional test result coverage.