As exposed in the Main Concepts, Artifacts are the corner stone in Microcks as they hold valuable information on how your API or microservices are expected to work. One of Microcks’s beauties is that it uses standard specifications or standard tooling files as Artifacts, allowing you to reuse existing assets. Microcks will use constraints and examples from them to build its knowledge base.

Microcks supports the following specifications and tooling file formats as artifacts:

We provide built-in parsers and importers for the following formats:

• SoapUI projects files starting with version 5.1 of SoapUI. See the Microcks’ SoapUI Conventions,
• Swagger v2 files. See the Microcks’ Swagger Conventions,
• OpenAPI v3.x files in either YAML or JSON format. See the Microcks’ OpenAPI Conventions,
• AsyncAPI v2.x and AsyncAPI v3.x files in either YAML or JSON format. See the Microcks’ AsyncAPI Conventions,
• Postman collections files with v2.x file format,
• gRPC / Protocol buffers v3 .proto files. See the Microcks’ gRPC Conventions,
• GraphQL Schema .graphql files. See the Microcks’ GraphQL Conventions,
• HTTP Archive Format (HAR) JSON files. See the Microcks’ HAR Conventions,

Microcks may require those artifact files to follow some conventions in order to collect the valuable information it need. This documentation is a reference of those different conventions for the above mentioned formats.