General questions
Press, partnerships, docs feedback, or anything that does not fit a public issue. We read every thread.
contact@testml.org// contact / channels.tml
Talk to the people who maintain TestML.
One inbox. One repo. One community. We are a small open-source team. We answer most threads in two business days. No sales calls. No demos. Just shipping a portable test format.
// 02 / channels
Pick the channel that fits the message.
Each topic has a home. Bug reports belong on GitHub. Roadmap chats belong in the community. Private notes belong in email. Route once. Reply fast.
Bug reports & feature ideas
Use GitHub issues for reproducible bugs, parser edge cases, runtime bridges, or spec proposals. Public threads only.
read the docs firstDiscussions & help
Stuck on a YAML pattern? Want to share a test bridge? Chat with other TestML users and maintainers in the open forum.
/community/Responsible disclosure
Found a parser flaw, sandbox escape, or runtime risk? Mail us privately. We triage within one business day.
contact@testml.org (subj: security)// 03 / writing.rfc
Help us reply fast.
A clear note saves a round-trip. Two short checklists below. Use the left one before you mail. Use the right one inside the message body.
Before you reach out
- 01Search the docs.Most syntax and bridge questions are already answered in the reference. Open it in a new tab.
- 02Check open issues.Your bug may already be filed. Add a thumbs-up or a fresh reproduction to bump priority.
- 03Try the latest release.We ship often. The fix you need may already be on the main branch tag.
- 04Skim the spec.If your question is about parser behaviour, the spec is the source of truth. Cite the section you mean.
What to include
- 01Runtime & version.Python 3.12, Node 22, Ruby 3.3 — and the TestML release tag you ran.
- 02Minimal repro.The shortest .tml file that fails, plus the exact CLI you used. Paste it inline.
- 03Expected vs actual.One line each. State what should happen. State what did happen. Skip long context.
- 04Logs & stack trace.Trim to the failing assertion. Wrap the block in triple backticks so it stays readable.
// 04 / next.steps
Skip the inbox. Start with the docs.
Many questions resolve faster on your own. The pages below cover install, syntax, runtime bridges, and the full spec. Try them first. Then write us anything that remains.