mmt-mcp 1.42.2-pre

package/dist/examples/intermediate/25_convert_to_mmt/bruno/converted/tests/create-user.mmt

@@ -0,0 +1,11 @@
+type: test
+title: Create user
+description: Generated from Bruno request "Create user".
+tags:
+  - bruno
+import:
+  createUser: ../api/create-user.mmt
+steps:
+  - call: createUser
+    id: iCreateUser
+    debug: true

package/dist/examples/intermediate/25_convert_to_mmt/http/README.md

@@ -0,0 +1,5 @@
+# HTTP convert (basic)
+
+`source.http` is a one-request HTTP file. **Convert to MMT...** produces an API file and a test that calls it under `converted/`.
+
+See the [convert overview](../README.md) for the other formats.

package/dist/examples/intermediate/25_convert_to_mmt/http/converted/api/ping.mmt

@@ -0,0 +1,9 @@
+type: api
+title: ping
+tags:
+  - http
+url: https://test.mmt.dev/json
+method: get
+format: text
+headers:
+  Accept: application/json

package/dist/examples/intermediate/25_convert_to_mmt/http/converted/tests/source-http.mmt

@@ -0,0 +1,11 @@
+type: test
+title: source.http
+description: Generated from HTTP request "ping".
+tags:
+  - http
+import:
+  ping: ../api/ping.mmt
+steps:
+  - call: ping
+    id: iPing
+    debug: true

package/dist/examples/intermediate/25_convert_to_mmt/openapi/README.md

@@ -0,0 +1,5 @@
+# OpenAPI convert (basic)
+
+`source.openapi.yaml` is a one-operation OpenAPI spec. **Convert to MMT...** produces `converted/api/get-sample-json.mmt`.
+
+See the [convert overview](../README.md) for the other formats.

package/dist/examples/intermediate/25_convert_to_mmt/openapi/converted/api/get-sample-json.mmt

@@ -0,0 +1,8 @@
+type: api
+title: Get sample JSON
+url: https://test.mmt.dev/json
+protocol: http
+method: get
+format: json
+headers:
+  trace: demo

package/dist/examples/intermediate/25_convert_to_mmt/postman/README.md

@@ -0,0 +1,7 @@
+# Postman convert (basic)
+
+`source.postman_collection.json` is a one-request collection. **Convert to MMT...** produces API, test, and suite files under `converted/`.
+
+The converted test keeps a `js` step that checks status with Multimeter helpers (`check_`, `equals_`, step `id` `iPing`). Postman `pm.*` is not available at runtime.
+
+See the [convert overview](../README.md) for the other formats.

package/dist/examples/intermediate/25_convert_to_mmt/postman/converted/api/ping.mmt

@@ -0,0 +1,23 @@
+type: api
+title: Ping
+outputs:
+  status: status
+  statusCode: status
+  id: body.id
+  name: body.name
+  description: body.description
+  version: body.version
+url: https://test.mmt.dev/json
+method: get
+format: json
+headers:
+  Accept: application/json
+examples:
+  - name: sample json
+    outputs:
+      status: 200
+      statusCode: 200
+      id: 1
+      name: Multimeter
+      description: API testing tool
+      version: 1.0.0

package/dist/examples/intermediate/25_convert_to_mmt/postman/converted/suites/collection.mmt

@@ -0,0 +1,7 @@
+type: suite
+title: Convert Example
+description: Generated from Postman collection folder "Convert Example".
+tags:
+  - postman
+items:
+  - ../tests/collection.mmt

package/dist/examples/intermediate/25_convert_to_mmt/postman/converted/tests/collection.mmt

@@ -0,0 +1,17 @@
+type: test
+title: Convert Example
+description: Generated from Postman collection folder "Convert Example".
+tags:
+  - postman
+import:
+  ping: ../api/ping.mmt
+steps:
+  - call: ping
+    id: iPing
+    expect:
+      status: 200
+    debug: true
+  # Postman `pm.*` is not available — Multimeter js using the step id instead.
+  - js: |-
+      check_(equals_(iPing.status, 200), 'check', 'iPing.status == 200', 'all', 'Ping (js)');
+      console.log('Ping name:', iPing.name);

package/dist/examples/intermediate/25_convert_to_mmt/wsdl/README.md

@@ -0,0 +1,5 @@
+# WSDL convert (basic)
+
+`source.wsdl` is a one-operation SOAP definition. **Convert to MMT...** produces `converted/api/ping.mmt`.
+
+See the [convert overview](../README.md) for the other formats.

package/dist/examples/intermediate/25_convert_to_mmt/wsdl/converted/api/ping.mmt

@@ -0,0 +1,21 @@
+type: api
+title: Ping
+inputs:
+  message: string
+url: https://test.mmt.dev/xml
+protocol: http
+method: post
+format: xml
+headers:
+  Content-Type: text/xml; charset=utf-8
+  SOAPAction: urn:Ping
+body: |-
+  <?xml version="1.0" encoding="utf-8"?>
+  <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tns="urn:convert">
+    <soapenv:Header/>
+    <soapenv:Body>
+      <tns:Ping>
+          <tns:message><<i:message>></tns:message>
+      </tns:Ping>
+    </soapenv:Body>
+  </soapenv:Envelope>

package/dist/examples/intermediate/26_yaml_expect_typing/README.md

@@ -0,0 +1,21 @@
+# YAML expect / check typing
+
+Live example for the value-typing rules used by `expect`, `check`, and `if`:
+
+| Written in YAML | Meaning |
+|---|---|
+| `== 200` / `200` | number |
+| `== "200"` | string `"200"` |
+| `null` | JSON null |
+| `"null"` | string `"null"` |
+| `omit` | field missing / omit keyword |
+| `"omit"` | string `"omit"` |
+| `!= null` | present (not omitted) |
+
+## Run
+
+```sh
+npx testlight run examples/intermediate/26_yaml_expect_typing/typing_test.mmt
+```
+
+Related: [Omit keyword](../22_omit_keyword/README.md) · [Check operators](../23_check_operators/README.md)

package/dist/examples/intermediate/26_yaml_expect_typing/typing_test.mmt

@@ -0,0 +1,29 @@
+type: test
+title: YAML expect and check typing
+description: |-
+  Covers the typing rules that broke several examples under testlight:
+  unquoted numbers/null/omit vs quoted string literals, and != null expects.
+steps:
+  - http: https://test.mmt.dev/echo
+    id: echo
+    method: post
+    body:
+      displayName: Alex
+      nickname: "omit"
+      bio: null
+      bioText: "null"
+    expect:
+      status: == 200
+      body.body.displayName: Alex
+      body.body.nickname: "omit"
+      body.body.bio: null
+      body.body.bioText: "null"
+  - check: ${echo.status} == 200
+  - check: ${echo.body.body.nickname} == "omit"
+  - check: ${echo.body.body.bioText} == "null"
+  - http: https://test.mmt.dev/echo?userId=1
+    id: query
+    method: get
+    expect:
+      status: == 200
+      body.query.userId: == "1"

package/dist/examples/intermediate/27_ai_judge/README.md

@@ -0,0 +1,31 @@
+# AI Judge
+
+Demonstrates `type: judge` with a `judge` step using soft **`expect`** and hard **`require`** (one report box).
+
+The demo imports both judges and runs **Gemini**. Change `judge: gemini` to `judge: ollama` to use the local engine.
+
+## Setup (Gemini — default)
+
+1. Create an API key at [Google AI Studio](https://aistudio.google.com/apikey).
+2. Set `api_key` in a `type: env` file or the Environment panel, then Reload.
+
+## Setup (Ollama)
+
+1. Install and run [Ollama](https://ollama.com/) on `http://127.0.0.1:11434`.
+2. Pull a model matching `model:` in `judges/ollama.mmt`, e.g. `ollama pull qwen2.5-coder:7b`.
+
+## Files
+
+| File | Role |
+|------|------|
+| `judges/gemini.mmt` | Judge resource (`engine: google`, used by the demo) |
+| `judges/ollama.mmt` | Judge resource (`engine: ollama`) |
+| `judge_demo.mmt` | Test with context / expect / require |
+
+## Run
+
+```bash
+npx testlight run examples/intermediate/27_ai_judge/judge_demo.mmt
+```
+
+Without a live engine, unit tests in `core` mock the HTTP layer; this example needs Gemini or Ollama.

package/dist/examples/intermediate/27_ai_judge/judge_demo.mmt

@@ -0,0 +1,33 @@
+type: test
+title: AI judge demo
+description: |
+  Evaluates a sample reply with soft expect and hard require
+  (one report box). Uses Gemini by default; switch the judge step
+  to ollama for a local model — see README.md.
+import:
+  gemini: ./judges/gemini.mmt
+  ollama: ./judges/ollama.mmt
+steps:
+  - const:
+      reply: "Yes. Under our policy you may return the item within 30 days of purchase."
+      expected: "The customer can return the product within 30 days."
+      policy: "Returns accepted within 30 days of purchase with receipt."
+
+  - judge: gemini
+    id: j1
+    title: Return-policy reply quality
+    context:
+      actual: ${reply}
+      expected: ${expected}
+      policy: ${policy}
+    expect:
+      answerRelevance: 0.75
+      semanticSimilarity: 0.75
+      criteria:
+        - The response should answer whether a return is allowed.
+        - The response should be concise.
+    require:
+      contextFaithfulness: 0.50
+      semanticSimilarity: 0.50
+
+  - print: "judge passed=${j1.passed}"

package/dist/examples/intermediate/27_ai_judge/judges/gemini.mmt

@@ -0,0 +1,12 @@
+type: judge
+title: Gemini quality judge
+engine: google
+model: gemini-3.5-flash-lite
+url: https://generativelanguage.googleapis.com/v1beta
+auth:
+  type: api-key
+  header: x-goog-api-key
+  value: e:api_key
+options:
+  temperature: 0
+  timeout: 30s

package/dist/examples/intermediate/27_ai_judge/judges/ollama.mmt

@@ -0,0 +1,8 @@
+type: judge
+title: Local quality judge
+engine: ollama
+model: qwen2.5-coder:7b
+url: http://127.0.0.1:11434
+options:
+  temperature: 0
+  timeout: 120s

package/dist/examples/professional/01_report_generation/README.md

@@ -0,0 +1,87 @@
+# Report Generation
+
+Demonstrates how to generate **test reports** in JUnit XML, HTML, Markdown, and MMT YAML formats — both via CLI flags and via the suite `export` field.
+
+## Structure
+
+```
+01_report_generation/
+├── api/
+│   └── echo.mmt                 # Simple echo API
+├── test/
+│   ├── pass_test.mmt            # A test that passes
+│   └── fail_test.mmt            # A test with a deliberate failure (for demo)
+├── suite.mmt                    # Suite with export field for auto-report
+├── reports/                     # Generated reports appear here
+└── README.md
+```
+
+## Files
+
+| File | Description |
+|---|---|
+| `api/echo.mmt` | Echo API used by both tests |
+| `test/pass_test.mmt` | Calls the echo API and asserts status 200 — should pass |
+| `test/fail_test.mmt` | Calls the echo API and checks for status 999 — deliberately fails |
+| `suite.mmt` | Suite with `export` field that auto-generates JUnit XML and HTML reports |
+
+## Report formats
+
+| Format | Flag | Default file | Description |
+|--------|------|--------------|-------------|
+| JUnit XML | `--report junit` | `test-results.xml` | CI/CD standard (GitHub Actions, Jenkins, etc.) |
+| HTML | `--report html` | `test-results.html` | Self-contained page with pass/fail indicators |
+| Markdown | `--report md` | `test-results.md` | GitHub-flavored tables, great for PRs |
+| MMT YAML | `--report mmt` | `test-results.mmt` | Native format, can be viewed in Multimeter |
+
+## Key concepts
+
+- **`--report FORMAT`** — CLI flag to generate a report after a test/suite run.
+- **`--report-file PATH`** — custom output path for the report.
+- **Suite `export`** — list of file paths in the suite file. Reports are auto-generated after the suite completes, with the format inferred from the file extension.
+- **`report` on checks** — controls reporting level: `all` (pass + fail), `fails` (only failures), `none` (silent).
+
+## How to use
+
+### In VS Code
+
+1. Open `suite.mmt` and click **Run**.
+2. After the run completes, click the **Export** button in the toolbar.
+3. Choose a format (JUnit XML, HTML, Markdown, or MMT YAML).
+
+### With the CLI
+
+Run the suite with automatic export (uses the `export` field):
+
+```sh
+npx testlight run examples/professional/01_report_generation/suite.mmt
+```
+
+Generate a specific report format:
+
+```sh
+# JUnit XML
+npx testlight run examples/professional/01_report_generation/suite.mmt --report junit
+
+# HTML
+npx testlight run examples/professional/01_report_generation/suite.mmt --report html
+
+# Markdown
+npx testlight run examples/professional/01_report_generation/suite.mmt --report md
+
+# MMT YAML
+npx testlight run examples/professional/01_report_generation/suite.mmt --report mmt
+```
+
+Custom output path:
+
+```sh
+npx testlight run examples/professional/01_report_generation/suite.mmt \
+  --report junit --report-file ./my-reports/output.xml
+```
+
+Run a single test with a report:
+
+```sh
+npx testlight run examples/professional/01_report_generation/test/pass_test.mmt --report junit
+```

package/dist/examples/professional/01_report_generation/api/echo.mmt

@@ -0,0 +1,13 @@
+type: api
+title: Echo API
+description: Simple echo endpoint for report examples
+inputs:
+  message: hello
+outputs:
+  status_code: status
+  echoed: body.body.message
+url: https://test.mmt.dev/echo
+method: post
+format: json
+body:
+  message: i:message

package/dist/examples/professional/01_report_generation/suite.mmt

@@ -0,0 +1,12 @@
+type: suite
+title: Report Generation Suite
+description: Runs passing and failing tests to demonstrate report output
+tags:
+  - example
+  - reports
+export:
+  - ./reports/results.xml
+  - ./reports/results.html
+items:
+  - test/pass_test.mmt
+  - test/fail_test.mmt

package/dist/examples/professional/01_report_generation/test/fail_test.mmt

@@ -0,0 +1,11 @@
+type: test
+title: Failing Test
+description: A test with a deliberate check failure (for report demo)
+import:
+  echo: ../api/echo.mmt
+steps:
+  - call: echo
+    id: result
+    inputs:
+      message: fail test
+  - check: ${result.status_code} == 999

package/dist/examples/professional/01_report_generation/test/pass_test.mmt

@@ -0,0 +1,17 @@
+type: test
+title: Passing Test
+description: A test that should pass
+import:
+  echo: ../api/echo.mmt
+steps:
+  - call: echo
+    id: result
+    inputs:
+      message: pass test
+    expect:
+      status_code: 200
+  - assert:
+      actual: ${result.status_code}
+      operator: ==
+      expected: 200
+      report: all

package/dist/examples/professional/02_tls_certificates/README.md

@@ -0,0 +1,113 @@
+# TLS Certificates
+
+Demonstrates how to configure **CA certificates** and **client certificates (mTLS)** in an environment file for secure HTTPS API calls.
+
+## Structure
+
+```
+02_tls_certificates/
+├── env.mmt                      # Environment file with certificates section
+├── api/
+│   └── secure_echo.mmt          # API that uses <<e:api_url>> (HTTPS)
+├── certs/                        # Place your certificate files here
+│   ├── ca.crt                   # CA certificate (not included — add your own)
+│   ├── client.crt               # Client certificate for mTLS (PEM)
+│   ├── client.key               # Client private key for mTLS (PEM)
+│   └── client.p12               # Optional PKCS#12 bundle instead of cert + key
+├── tls_test.mmt                  # Test that calls the secure API
+└── README.md
+```
+
+## Files
+
+| File | Description |
+|---|---|
+| `env.mmt` | Environment file with `certificates` section — CA paths and client cert config |
+| `api/secure_echo.mmt` | API using `<<e:api_url>>` to call an HTTPS endpoint |
+| `tls_test.mmt` | Test that calls the secure API with certificate config |
+
+## Certificate configuration
+
+The `certificates` section in `env.mmt` has two parts:
+
+### CA certificates
+
+```yaml
+certificates:
+  server_ca: "./certs/ca.crt"
+```
+
+Add a path to your CA PEM file. This is used to trust custom certificate authorities (e.g., internal company CAs).
+
+### Client certificates (mTLS)
+
+Use either PEM `cert` + `key`, or a PKCS#12 bundle in `pfx` (`.p12` or `.pfx`):
+
+```yaml
+certificates:
+  clients:
+    - name: "Example API"
+      host: "*.example.com"
+      cert: "./certs/client.crt"
+      key: "./certs/client.key"
+      passphrase_env: "CLIENT_CERT_PASS"
+    - name: "Example API PKCS#12"
+      host: "*.internal.example.com"
+      pfx: "./certs/client.p12"
+      passphrase_env: "CLIENT_CERT_PASS"
+```
+
+| Field | Description |
+|---|---|
+| `name` | Display name for the certificate |
+| `host` | Host pattern to match (e.g., `*.api.example.com` or `*` for all) |
+| `cert` | Path to client certificate file (PEM) |
+| `key` | Path to private key file (PEM) |
+| `pfx` | Path to PKCS#12 bundle (`.p12` or `.pfx`) — alternative to `cert` + `key` |
+| `passphrase_env` | Environment variable name containing the key or bundle passphrase |
+| `passphrase_plain` | Plain text passphrase (avoid in shared configs) |
+
+## Enable/disable settings (VS Code workspace)
+
+These are managed via the UI, not in the YAML file:
+
+| Setting | Default | Description |
+|---|---|---|
+| CA Enabled | `false` | Enable custom CA certificates |
+| Client Enabled | `true` | Enable/disable individual client certs |
+
+## Supported formats
+
+- **PEM:** `.pem`, `.crt`, `.cer`, `.key` for `server_ca`, `cert`, and `key`
+- **PKCS#12:** `.p12` or `.pfx` for `pfx` (client bundle)
+
+Working PKCS#12 samples live next to the PEM files in `06_mtls_mock_server` and `08_external_mtls_badssl`. Current Node runtimes need AES-based PKCS#12; older RC2/3DES bundles fail with `Unsupported PKCS12 PFX data`. Re-export if needed:
+
+```sh
+openssl pkcs12 -export \
+  -in client.crt -inkey client.key \
+  -out client.p12 \
+  -keypbe AES-256-CBC -certpbe AES-256-CBC -macalg sha256
+```
+
+## How to use
+
+### In VS Code
+
+1. Place your certificate files in the `certs/` folder.
+2. Open the `env.mmt` file and switch to the **Certificates** tab to configure paths and toggle settings.
+3. Set the environment in the **Environment** panel.
+4. Open `tls_test.mmt` and click **Run**.
+
+### With the CLI
+
+```sh
+# Set passphrase via environment variable
+export CLIENT_CERT_PASS="secret123"
+
+# Run the test with the env file
+npx testlight run examples/professional/02_tls_certificates/tls_test.mmt \
+  --env-file examples/professional/02_tls_certificates/env.mmt
+```
+
+> **Note:** This example uses `https://test.mmt.dev/echo` which does not require client certificates. To test mTLS, point `api_url` at your own server that requires client certs.

package/dist/examples/professional/02_tls_certificates/api/secure_echo.mmt

@@ -0,0 +1,13 @@
+type: api
+title: Secure API Call
+description: Calls an HTTPS endpoint (certificates configured via env file)
+inputs:
+  message: hello secure
+outputs:
+  status_code: status
+  echoed: body.body.message
+url: <<e:api_url>>/echo
+method: post
+format: json
+body:
+  message: i:message

package/dist/examples/professional/02_tls_certificates/env.mmt

@@ -0,0 +1,17 @@
+type: env
+variables:
+  api_url:
+    - "https://test.mmt.dev"
+
+certificates:
+  server_ca: "./certs/ca.crt"
+  clients:
+    - name: "Example API"
+      host: "*.example.com"
+      cert: "./certs/client.crt"
+      key: "./certs/client.key"
+      passphrase_env: "CLIENT_CERT_PASS"
+    - name: "Example API PKCS#12"
+      host: "*.internal.example.com"
+      pfx: "./certs/client.p12"
+      passphrase_env: "CLIENT_CERT_PASS"

package/dist/examples/professional/02_tls_certificates/tls_test.mmt

@@ -0,0 +1,12 @@
+type: test
+title: TLS Certificate Test
+description: Demonstrates making API calls with certificate configuration
+import:
+  secureEcho: ./api/secure_echo.mmt
+steps:
+  - call: secureEcho
+    id: result
+    inputs:
+      message: hello from TLS test
+    expect:
+      status_code: 200

package/dist/examples/professional/03_load_test/README.md

@@ -0,0 +1,39 @@
+# Load Test Example
+
+This example shows a beta `type: loadtest` file that runs one normal `type: test` scenario repeatedly with concurrency, ramp-up, and report exports.
+
+## Files
+
+| File | Purpose |
+|------|---------|
+| `echo_api.mmt` | API request sent to the public test server |
+| `echo_test.mmt` | Functional scenario run by each load test iteration |
+| `loadtest.mmt` | Load test wrapper with `threads`, `repeat`, `rampup`, and `export` |
+
+## Run from VS Code
+
+Open `loadtest.mmt` and use the Multimeter Run action. The panel shows live load metrics while the run is active.
+
+## Run from CLI
+
+```sh
+npx testlight run examples/professional/03_load_test/loadtest.mmt
+```
+
+The `export` field writes reports after the run:
+
+- `reports/echo-load.mmt` — native structured load report
+- `reports/echo-load.html` — visual load report with charts
+- `reports/echo-load.md` — Markdown load report with Mermaid charts
+- `reports/echo-load.xml` — CI-compatible JUnit XML properties
+
+You can also generate a one-off report path:
+
+```sh
+npx testlight run examples/professional/03_load_test/loadtest.mmt --report html --report-file reports/load.html
+```
+
+## Learn more
+
+- [Load Test docs](../../../docs/files/loadtest/index.md)
+- [Reports docs](../../../docs/files/report/reference.md#load-report-kind-load)

package/dist/examples/professional/03_load_test/echo_api.mmt

@@ -0,0 +1,12 @@
+type: api
+title: Echo API for Load Test
+description: Posts a message to the public test server and extracts the echoed message.
+inputs:
+  message: load-test
+outputs:
+  echoed_message: body.body.message
+url: https://test.mmt.dev/echo
+method: post
+format: json
+body:
+  message: i:message

package/dist/examples/professional/03_load_test/echo_test.mmt

@@ -0,0 +1,14 @@
+type: test
+title: Echo Scenario
+description: Scenario used by the load test. Each iteration calls the echo API and validates the response.
+import:
+  echo: echo_api.mmt
+inputs:
+  message: load-test
+steps:
+  - call: echo
+    id: result
+    inputs:
+      message: i:message
+    expect:
+      echoed_message: <<i:message>>