import_functional_tests
Import existing tests from your codebase to associate them with functional objectives, verifying associations and reporting rejected mappings.
Instructions
Register existing tests from the codebase against a model's functional objectives, so tests you already have count toward functional conformance — not only Mipiti-specified tests.
Scan the repo's test suite and pass the tests here. Optionally associate each
with the objective ids it covers (from list_functional_objectives); the
platform verifies each association is applicable before accepting it and
returns any it rejected under rejected_mappings. A test with no (or a
rejected) association is still imported, unmapped, so it can be associated
later.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| model_id | Yes | ID of the threat model. | |
| tests_json | Yes | A JSON array of test objects. Each object supports ``test_name``, ``file_path``, ``framework``, ``description``, ``status`` (not_implemented | implemented | verified — an operator claim; an independent CI run is what verifies it), and ``functional_objective_ids`` (list of objective ids the test covers). At least ``test_name`` or ``description`` is required per test; the rest are optional. | |
| server_version | Yes |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||