FAQ
Short answers to the questions the trial, the webinars and the first calls have been bringing up. If yours is missing, ask — a human replies.
FAQ
Short answers
- How do I try Metrix right now?
- Grab the 7-day trial at t4test.de/trial. Three-field form, then a direct download of the Windows ZIP plus a time-limited licence. Full product, no feature gating.
- What are the system requirements?
- Windows 10/11 x64, 8 GB RAM minimum (16 GB for larger books), 1 GB disk for the install plus space for extracted ALM data. The JRE ships with the installer; no separate Java install. Linux and macOS builds on request.
- Is my data sent to T4Test or to the cloud?
- No. Metrix runs on-premise. The licence validates locally — no phone-home, no telemetry. Nothing in your book or your extracted data leaves your machine.
- How is Metrix different from Power BI or Tableau?
- Three ways. Metrix runs air-gapped — no service needed. Metric definitions are text files in git, not clicks in a UI. And it's designed around engineering structure (requirements, traces, test coverage) rather than generic data cubes.
- Can I attend a live demo?
- Yes. The Measuring What Matters webinar series runs eight 30-minute sessions, 24 Nov to 17 Dec 2026, Tuesdays and Thursdays at 18:00 CET. Open-join on Microsoft Teams, no registration. Schedule at t4test.de/events.html.
- Does PROmeter Metrix work air-gapped?
- Yes. Both the editor and the executor run without internet access once a license is installed. The runtime only reaches the source systems you configure.
- How steep is the learning curve for a metric author?
- About a day for a first book if the analyst already knows the source query language (JQL, DXL, SQL, or the shape of the CSV). Books are text under the hood, so the mental model is closer to "wrote a config" than "wrote code."
- Can we use it with GitHub / GitLab / Azure DevOps / Polarion?
- Not natively today. CSV import handles most of these via a scheduled export. Native connectors ship when there is enough customer demand — ask us.
- Where is the extracted data stored?
- In a local ArcadeDB directory of your choosing. The default path is your user profile; production installs typically point it at a persistent volume.
- Can I run it in CI?
- Yes — the executor is a single JVM invocation with a well-defined exit-code contract. GitHub Actions / GitLab CI examples are in the Quickstart.
- Can I export a report to PDF?
- The rendered HTML has a print stylesheet; use the browser's Print → Save as PDF flow. There is no built-in PDF exporter — the print flow round-trips cleanly enough that adding one hasn't been prioritized.
- Can I bundle a report for email?
- Zip the output folder; the recipient unzips and double-clicks the
.html. Everything they need is inside. - What happens if a source system is unreachable?
- Extraction fails with a clear error pointing at the specific source. Renders that depend on cached data still work; renders that require a fresh pull skip cleanly. No hangs.
- Is there a public API?
- The editor and CLI are the public API today. A programmatic embedding surface exists but is not covered by the standard license.
- How do you handle secrets in books?
- Connection credentials live in a separate config file (vault-encrypted in production), never in the
.mxb. The book only references the connection profile by name. - What's the upgrade path for a book across versions?
- Books carry a
schemaVersion. The verifier reports incompatibilities before executing; a small migration tool bumps common shape changes automatically. - How do individual developers run the same book the nightly runs?
- With a reviewer-mode license they open the shared
.mxbin the desktop editor, narrow the parameters or scope to what they own, and execute locally. Extraction is cached, so a re-run after fixing a review finding takes seconds. Same book → same number, no reconciliation needed.