mmt-mcp 1.42.2-pre

package/dist/examples/intermediate/11_control_flow/repeat_delay_test.mmt

@@ -0,0 +1,24 @@
+type: test
+title: Control Flow — repeat and delay
+description: Demonstrates repeat (count-based and time-based) and delay steps
+import:
+  echo: ./api/echo.mmt
+steps:
+  - print: Starting repeat 3 times...
+  - repeat: 3
+    steps:
+      - call: echo
+        id: poll
+        inputs:
+          message: polling
+      - check: ${poll.status_code} == 200
+      - delay: 500
+  - print: Starting time-based repeat for 3 seconds...
+  - repeat: 3s
+    steps:
+      - call: echo
+        id: tick
+        inputs:
+          message: Hi
+      - delay: 1s
+  - print: All repeats completed

package/dist/examples/intermediate/12_random_values/README.md

@@ -0,0 +1,59 @@
+# Random Values
+
+Demonstrates built-in `r:xxx` tokens in YAML files. These tokens generate random values at runtime without needing a `js` step.
+
+## Structure
+
+```
+12_random_values/
+├── api/
+│   └── random_echo.mmt          # API using random tokens in the request body
+├── random_values_test.mmt       # Test that calls the API and validates the echoed values
+└── README.md
+```
+
+## Files
+
+| File | Description |
+|---|---|
+| `api/random_echo.mmt` | Sends random UUID, email, first name, integer, and boolean values |
+| `random_values_test.mmt` | Calls the API and checks that the generated values were echoed back |
+
+## Example tokens
+
+```yaml
+body:
+  id: r:uuid
+  email: r:email
+  name: r:first_name
+  lucky_number: r:int
+  active: r:bool
+  request_id: req-<<r:uuid>>
+```
+
+## Key concepts
+
+- **Standalone `r:xxx` values** keep their native type. For example, `r:int` becomes a number and `r:bool` becomes a boolean.
+- **Embedded tokens** must use `<< >>`. In this example, `req-<<r:uuid>>` generates a string with a random suffix.
+- **No JS required** — random values can be used directly in API `body`, `headers`, `query`, `cookies`, `url`, and input defaults.
+- **Inline `expect`** checks the echoed values without adding separate `assert` or `check` steps.
+
+## How to use
+
+### In VS Code
+
+1. Open `random_values_test.mmt`.
+2. Click **Run** to execute the test.
+3. Inspect the response to see the generated values change on each run.
+
+### With the CLI
+
+```sh
+npx testlight run examples/intermediate/12_random_values/random_values_test.mmt
+```
+
+## Next steps
+
+- See [Simple Mock Server](../18_simple_mock_server/) for random tokens in mock server responses.
+- See [JavaScript Helpers](../14_javascript_helpers/) for the JavaScript `Random.*` helpers.
+- See [API docs](../../../docs/files/api/index.md) for the full list of supported random tokens.

package/dist/examples/intermediate/12_random_values/api/random_echo.mmt

@@ -0,0 +1,21 @@
+type: api
+title: Random Echo
+description: Sends random YAML tokens and extracts the echoed values from the response
+outputs:
+  random_id: body.body.id
+  random_email: body.body.email
+  random_name: body.body.name
+  lucky_number: body.body.lucky_number
+  active: body.body.active
+  request_id: body.body.request_id
+  request_method: body.method
+url: https://test.mmt.dev/echo
+method: post
+format: json
+body:
+  id: r:uuid
+  email: r:email
+  name: r:first_name
+  lucky_number: r:int
+  active: r:bool
+  request_id: req-<<r:uuid>>

package/dist/examples/intermediate/12_random_values/random_values_test.mmt

@@ -0,0 +1,15 @@
+type: test
+title: Random Values
+description: Calls an API that uses r:xxx tokens and validates the echoed results
+import:
+  randomEcho: ./api/random_echo.mmt
+steps:
+  - call: randomEcho
+    id: result
+    expect:
+      request_method: POST
+      random_id: != null
+      random_email: =* [a-z._]+@[a-z]+\.[a-z]+
+      random_name: != null
+      lucky_number: != null
+      request_id: =^ req-

package/dist/examples/intermediate/13_stages_and_conditions/README.md

@@ -0,0 +1,58 @@
+# Stages and Conditions
+
+Demonstrates **parallel stages** with `after` dependencies and **conditional stage execution** using `condition`.
+
+## Structure
+
+```
+13_stages_and_conditions/
+├── api/
+│   ├── login.mmt               # Login API
+│   ├── get_profile.mmt         # Profile API
+│   └── get_settings.mmt        # Settings API
+├── stages_test.mmt              # Test with parallel stages, after, and condition
+└── README.md
+```
+
+## Files
+
+| File | Description |
+|---|---|
+| `api/login.mmt` | Simulates login, outputs a token |
+| `api/get_profile.mmt` | Fetches profile using a token |
+| `api/get_settings.mmt` | Fetches settings using a token |
+| `stages_test.mmt` | Three stages: `auth` runs first, then `profile` and `settings` run in parallel after auth succeeds |
+
+## Execution flow
+
+```
+auth (login)
+  ├── condition met ──► profile  ┐
+  │                               ├── run in parallel
+  └── condition met ──► settings ┘
+```
+
+1. **auth** stage runs first (login).
+2. **profile** and **settings** both have `after: auth` — they wait for auth to finish.
+3. Both have `condition: doLogin.status_code == 200` — they are skipped if login fails.
+4. Once auth passes, profile and settings run **in parallel**.
+
+## Key concepts
+
+- **`stages`** — groups of steps that start concurrently by default.
+- **`after`** — declares a dependency so the stage waits for another stage to complete first. Can be a single string or an array.
+- **`condition`** — skips the stage if the expression is false. Uses the same syntax as `assert`/`check`.
+- **Parallelism** — stages without `after` dependencies run simultaneously. Stages with the same `after` also run in parallel with each other.
+
+## How to use
+
+### In VS Code
+
+1. Open `stages_test.mmt` and click **Run**.
+2. The Flow panel shows the stage graph with dependencies.
+
+### With the CLI
+
+```sh
+npx testlight run examples/intermediate/13_stages_and_conditions/stages_test.mmt
+```

package/dist/examples/intermediate/13_stages_and_conditions/api/get_profile.mmt

@@ -0,0 +1,13 @@
+type: api
+title: Get Profile
+description: Fetches a user profile
+inputs:
+  token: placeholder
+outputs:
+  status_code: status
+  name: body.body.token
+url: https://test.mmt.dev/echo
+method: post
+format: json
+body:
+  token: i:token

package/dist/examples/intermediate/13_stages_and_conditions/api/get_settings.mmt

@@ -0,0 +1,13 @@
+type: api
+title: Get Settings
+description: Fetches user settings
+inputs:
+  token: placeholder
+outputs:
+  status_code: status
+  theme: body.body.token
+url: https://test.mmt.dev/echo
+method: post
+format: json
+body:
+  token: i:token

package/dist/examples/intermediate/13_stages_and_conditions/api/login.mmt

@@ -0,0 +1,15 @@
+type: api
+title: Login API
+description: Simulates login and returns a token
+inputs:
+  username: alice
+  password: secret
+outputs:
+  status_code: status
+  token: body.body.username
+url: https://test.mmt.dev/echo
+method: post
+format: json
+body:
+  username: i:username
+  password: i:password

package/dist/examples/intermediate/13_stages_and_conditions/stages_test.mmt

@@ -0,0 +1,40 @@
+type: test
+title: Stages and Conditions
+description: Demonstrates parallel stages with after dependencies and conditional execution
+import:
+  login: ./api/login.mmt
+  getProfile: ./api/get_profile.mmt
+  getSettings: ./api/get_settings.mmt
+stages:
+  - id: auth
+    title: Authentication
+    steps:
+      - call: login
+        id: doLogin
+        inputs:
+          username: alice
+          password: secret
+        expect: 
+          status_code: 200
+  - id: profile
+    title: Fetch Profile
+    condition: ${doLogin.status_code} == 200
+    after: auth
+    steps:
+      - call: getProfile
+        id: userProfile
+        inputs:
+          token: ${doLogin.token}
+        expect: 
+          status_code: 200
+  - id: settings
+    title: Fetch Settings
+    condition: ${doLogin.status_code} == 200
+    after: auth
+    steps:
+      - call: getSettings
+        id: userSettings
+        inputs:
+          token: ${doLogin.token}
+        expect: 
+          status_code: 200

package/dist/examples/intermediate/14_javascript_helpers/README.md

@@ -0,0 +1,59 @@
+# JavaScript Helpers
+
+Demonstrates **`js` steps**, **imported JS helpers**, and **runner globals** like `Random.*`, `setenv_()`, and `report_()`.
+
+## Structure
+
+```
+14_javascript_helpers/
+├── helpers/
+│   └── helpers.js               # Plain JS functions (auto-exported)
+├── api/
+│   └── echo.mmt                 # Simple echo API
+├── js_test.mmt                  # Test using js steps and imported helpers
+└── README.md
+```
+
+## Files
+
+| File | Description |
+|---|---|
+| `helpers/helpers.js` | Top-level functions `greet()`, `sum()`, and `formatDate()` |
+| `api/echo.mmt` | Echo API used for validation |
+| `js_test.mmt` | Test that imports the JS file and uses runner globals in `js` steps |
+
+## Key concepts
+
+- **JS helper import** — import `.js`/`.cjs`/`.mjs` files in the `import` section. They are loaded once per run.
+  ```yaml
+  import:
+    helpers: ./helpers/helpers.js
+  ```
+- **Plain functions** — write normal top-level functions (or `const fn = () => {}`). Multimeter exposes them on the import alias automatically. `module.exports = { ... }` still works if you prefer it.
+- **`js` step** — inline JavaScript block. Has access to all imports and runner globals.
+  ```yaml
+  - js: |
+      const greeting = helpers.greet('World');
+  ```
+- **Runner globals** available in `js` steps:
+
+  | Global | Description |
+  |--------|-------------|
+  | `Random.*` | `randomUUID()`, `randomEmail()`, `randomInt()`, etc. |
+  | `setenv_(vars)` | Set environment variables at runtime from an object |
+  | `report_(type, comparison, title, details, passed)` | Emit a check/assert result |
+  | `console.log/warn/error` | Log to the output panel |
+  | `send_(request)` | Send an HTTP request directly |
+
+## How to use
+
+### In VS Code
+
+1. Open `js_test.mmt` and click **Run**.
+2. The Log panel shows `console.log` output and the custom `report_` check result.
+
+### With the CLI
+
+```sh
+npx testlight run examples/intermediate/14_javascript_helpers/js_test.mmt
+```

package/dist/examples/intermediate/14_javascript_helpers/api/echo.mmt

@@ -0,0 +1,13 @@
+type: api
+title: Echo API
+description: Simple echo for JS helper tests
+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/intermediate/14_javascript_helpers/js_test.mmt

@@ -0,0 +1,31 @@
+type: test
+title: JavaScript Helpers
+description: Demonstrates js steps, imported JS modules, and runner globals
+import:
+  helpers: ./helpers/helpers.js
+  echo: ./api/echo.mmt
+steps:
+  # Use an imported JS module function
+  - js: |
+      const greeting = helpers.greet('Multimeter');
+      console.log('Greeting:', greeting);
+  
+  # Use runner globals: Random functions
+  - js: |
+      const randomId = Random.randomUUID();
+      const randomEmail = Random.randomEmail();
+      console.log('Random UUID:', randomId);
+      console.log('Random email:', randomEmail);
+
+  # Use setenv_ to promote a value to an env variable
+  - js: |
+      const token = Random.randomUUID();
+      setenv_({ DYNAMIC_TOKEN: token });
+      console.log('Set DYNAMIC_TOKEN to:', token);
+
+  # Use the helpers module for computation
+  - js: |
+      const total = helpers.sum([10, 20, 30]);
+      console.log('Sum:', total);
+      const now = helpers.formatDate(Date.now());
+      console.log('Current time:', now);

package/dist/examples/intermediate/15_http_files/README.md

@@ -0,0 +1,25 @@
+# HTTP file examples
+
+These examples show `.http` files that can be opened through **Open With...** → **Multimeter HTTP Test Editor**, or **Open as MMT**.
+
+The header has a selector and **Save as MMT**. **All** runs every request as one test; pick a request to Send it. The Test and API UIs are the same as for `.mmt` files.
+
+All live requests target the public [test.mmt.dev](https://test.mmt.dev) test server.
+
+## Files
+
+- `auth_user_flow.http`: login, create user, verify bearer auth, update user, and delete user flow with captured variables.
+- `echo_posts.http`: create, fetch, search, and delete post flow using echo and status endpoints on test.mmt.dev.
+- `import_http_in_test.mmt`: a Multimeter test that imports a `.http` file and calls it like any other test import.
+
+## Importing HTTP files from MMT
+
+`.http` and `.https` files can be imported from `type: test` files. Multimeter converts them to test flows internally, so a normal `call` step can run the HTTP file.
+
+```yaml
+type: test
+import:
+	posts: echo_posts.http
+steps:
+	- call: posts
+```

package/dist/examples/intermediate/15_http_files/import_http_in_test.mmt

@@ -0,0 +1,8 @@
+type: test
+title: Import HTTP file in test
+description: Runs an imported .http file as a normal test call.
+import:
+  posts: echo_posts.http
+steps:
+  - call: posts
+    title: Run echo HTTP flow

package/dist/examples/intermediate/16_bruno_files/README.md

@@ -0,0 +1,36 @@
+# Bruno file examples
+
+These examples show `.bru` files that can be opened through **Open With...** → **Multimeter Bruno Test Editor**, or **Open as MMT**.
+
+Use {{btn:list-tree}} in the header to pick **All** (one test) or a single request (API **Send**). See [Spec editor](../../docs/integration/spec-editor.md) for the full picker guide. Hover a row for {{btn:save-as}}.
+
+## Files
+
+- `library/`: a Bruno collection (`bruno.json` plus several request files). Open `bruno.json` for the full collection, or any `.bru` for that request alone.
+- `checkout_book_complete.bru`: one complete standalone request with meta, docs, vars, headers, query params, bearer auth, a JSON body, and several `expect` checks.
+- `get_profile.bru`: a simple Bruno GET request with variables, headers, bearer auth, query params, and assertions.
+- `create_user_json.bru`: a POST request with a JSON body and bearer auth.
+- `update_profile_form.bru`: a PUT request with a form-urlencoded body.
+- `xml_echo.bru`: a POST request with an XML text body.
+- `import_bruno_in_test.mmt`: a Multimeter test that imports a `.bru` file and calls it like any other test import.
+
+## Importing Bruno Files From MMT
+
+`.bru` files can be imported from `type: test` files. Multimeter converts them to test flows internally, so a normal `call` step can run the Bruno request.
+
+```yaml
+type: test
+title: Import Bruno request
+import:
+  profile: get_profile.bru
+  createUser: create_user_json.bru
+  updateProfile: update_profile_form.bru
+  xmlEcho: xml_echo.bru
+  checkout: checkout_book_complete.bru
+steps:
+  - call: profile
+  - call: createUser
+  - call: updateProfile
+  - call: xmlEcho
+  - call: checkout
+```

package/dist/examples/intermediate/16_bruno_files/import_bruno_in_test.mmt

@@ -0,0 +1,18 @@
+type: test
+title: Import Bruno request
+description: Run a Bruno .bru request through a Multimeter test flow.
+tags: [bruno, import]
+
+import:
+  profile: get_profile.bru
+  createUser: create_user_json.bru
+  updateProfile: update_profile_form.bru
+  xmlEcho: xml_echo.bru
+  checkout: checkout_book_complete.bru
+
+steps:
+  - call: profile
+  - call: createUser
+  - call: updateProfile
+  - call: xmlEcho
+  - call: checkout

package/dist/examples/intermediate/16_bruno_files/library/README.md

@@ -0,0 +1,8 @@
+# Library Bruno collection
+
+A small Bruno collection (`bruno.json` plus one `.bru` file per request).
+
+- Open **`bruno.json`** with **Open as MMT** to run the whole collection (**All** as one test) or pick any request from the selector.
+- Open a single **`.bru`** to work with that request only (test + API). Sibling requests are not listed.
+
+All requests hit [test.mmt.dev](https://test.mmt.dev).

package/dist/examples/intermediate/17_api_authentication/README.md

@@ -0,0 +1,35 @@
+# API Authentication
+
+Examples of `type: api` files that add authentication to requests.
+
+## Files
+
+| File | Description |
+|---|---|
+| `get_with_basic_auth.mmt` | Sends a GET request with Basic username/password authentication |
+| `get_with_bearer_auth.mmt` | Sends a GET request with a Bearer token |
+| `get_with_apikey_auth.mmt` | Sends a GET request with an API key in a custom header |
+
+## How to use
+
+### In VS Code
+
+1. Open any `.mmt` file in this folder.
+2. Click **Run** in the editor to execute the API call.
+3. Inspect the request headers in the output panel.
+
+### With the CLI
+
+```sh
+npx testlight run examples/intermediate/17_api_authentication/get_with_basic_auth.mmt
+npx testlight run examples/intermediate/17_api_authentication/get_with_bearer_auth.mmt
+npx testlight run examples/intermediate/17_api_authentication/get_with_apikey_auth.mmt
+```
+
+## Key concepts
+
+- **Basic auth** sends a username and password as an Authorization header.
+- **Bearer auth** sends a token as an Authorization header.
+- **API key auth** sends a configured key in a configured header.
+
+See [API docs](../../../docs/files/api/index.md) for the full `.mmt` API reference.

package/dist/examples/intermediate/17_api_authentication/get_with_apikey_auth.mmt

@@ -0,0 +1,10 @@
+type: api
+title: Get with API key auth
+description: Sends a GET request with an API key in a custom header
+url: https://test.mmt.dev/echo
+method: get
+format: json
+auth:
+  type: api-key
+  header: X-API-Key
+  value: abc123def456

package/dist/examples/intermediate/17_api_authentication/get_with_basic_auth.mmt

@@ -0,0 +1,10 @@
+type: api
+title: Get with Basic auth
+description: Sends a GET request with Basic username/password authentication
+url: https://test.mmt.dev/echo
+method: get
+format: json
+auth:
+  type: basic
+  username: admin
+  password: secret123

package/dist/examples/intermediate/17_api_authentication/get_with_bearer_auth.mmt

@@ -0,0 +1,9 @@
+type: api
+title: Get with Bearer auth
+description: Sends a GET request with Bearer token authentication
+url: https://test.mmt.dev/echo
+method: get
+format: json
+auth:
+  type: bearer
+  token: my-secret-token

package/dist/examples/intermediate/18_simple_mock_server/README.md

@@ -0,0 +1,92 @@
+# Simple Mock Server
+
+A self-contained example that defines a mock server in an `.mmt` file and runs tests against it — covering **GET** and **POST** requests with and without parameters.
+
+## Structure
+
+```
+18_simple_mock_server/
+├── server/
+│   └── mock_server.mmt          # Mock server definition (type: server)
+├── api/
+│   ├── get_health.mmt           # GET /health — no parameters
+│   ├── get_user.mmt             # GET /users/:id — path parameter
+│   ├── create_user.mmt          # POST /users — JSON body
+│   └── search.mmt               # GET /search?q=... — query parameter
+├── test/
+│   ├── health_test.mmt          # Test the health endpoint
+│   ├── user_test.mmt            # Test GET and POST user endpoints
+│   └── search_test.mmt          # Test the search endpoint
+├── suite.mmt                    # Suite that starts the server and runs all tests
+└── README.md
+```
+
+## Files
+
+### Server
+
+| File | Description |
+|---|---|
+| `server/mock_server.mmt` | Defines a mock server on port 9099 with HTTP endpoints |
+
+### APIs
+
+| File | Method | Path | Parameters |
+|---|---|---|---|
+| `api/get_health.mmt` | GET | `/health` | None |
+| `api/get_user.mmt` | GET | `/users/:id` | Path param `user_id` |
+| `api/create_user.mmt` | POST | `/users` | JSON body (`name`, `email`) |
+| `api/search.mmt` | GET | `/search?q=...` | Query param `q` |
+
+### Tests
+
+| File | Description |
+|---|---|
+| `test/health_test.mmt` | Starts the server, calls GET `/health`, asserts `status == ok` |
+| `test/user_test.mmt` | Starts the server, fetches a user by ID, creates a user via POST, asserts fields |
+| `test/search_test.mmt` | Starts the server, calls GET `/search` with a query param, asserts response |
+
+### Suite
+
+| File | Description |
+|---|---|
+| `suite.mmt` | Uses `servers:` to start the mock server, then runs all three tests in parallel |
+
+## Key concepts
+
+- **`type: server`** — defines a mock server with endpoints, a port, and optional fallback/CORS/delay settings.
+- **`run` step in tests** — starts the mock server before making API calls. If the server is already running, `run` is a no-op.
+- **Path parameters** — use `:param` in server endpoint paths (e.g. `/users/:id`); reference them in the response body with `"${url.id}"`.
+- **Request echo** — use `${body.field}`, `${header.name}`, and `${query.param}` to echo parsed request data back in responses.
+- **Dynamic tokens** — `r:uuid` generates a random UUID, `c:date` inserts the current date.
+- **Fallback** — any request that doesn't match an endpoint returns the fallback response (404 in this example).
+
+## How to use
+
+### In VS Code
+
+1. Open any test file (e.g. `test/health_test.mmt`) and click **Run**.
+   The test starts the mock server automatically via the `run` step, calls the API, and checks the result.
+2. Or open `suite.mmt` and click **Run** to execute all tests at once.
+
+### With the CLI
+
+Run individual tests:
+
+```sh
+npx testlight run examples/intermediate/18_simple_mock_server/test/health_test.mmt
+npx testlight run examples/intermediate/18_simple_mock_server/test/user_test.mmt
+npx testlight run examples/intermediate/18_simple_mock_server/test/search_test.mmt
+```
+
+Run the full suite:
+
+```sh
+npx testlight run examples/intermediate/18_simple_mock_server/suite.mmt
+```
+
+Override inputs:
+
+```sh
+npx testlight run examples/intermediate/18_simple_mock_server/test/user_test.mmt -e user_id=99
+```

package/dist/examples/intermediate/18_simple_mock_server/api/create_user.mmt

@@ -0,0 +1,15 @@
+type: api
+title: Create User
+description: POST request to create a new user
+inputs:
+  name: Alice
+  email: alice@example.com
+outputs:
+  id: body.id
+  message: body.message
+url: http://localhost:9099/users
+method: post
+format: json
+body:
+  name: i:name
+  email: i:email

package/dist/examples/intermediate/18_simple_mock_server/api/get_health.mmt

@@ -0,0 +1,9 @@
+type: api
+title: Health Check
+description: GET request to the health endpoint (no parameters)
+outputs:
+  status_field: body.status
+  uptime: body.uptime
+url: http://localhost:9099/health
+method: get
+format: json