Artifacts Reference

🗓️ Last updated on May 27, 2024 | 2 | Improve this page

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:

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.

Still Didn’t Find Your Answer?

Join our community and get the help you need. Engage with other members, ask questions, and share knowledge to resolve your queries and expand your understanding.

Join the community