/termsRFC-styled · v2.1

Terms of Service for the TestML project

These rules govern your use of TestML. Read them in plain text. The clauses are short. The license is open. The promise is simple. Write tests once. Run them everywhere.

Free to useOpen-source licenseNo vendor lock-inPlain-text rules
// What we promise

Four things to read first

The clauses below set the legal frame. These four lines set the tone. If you skim the page, skim these. Then read the clause that fits your case.

promise

No fee, ever

Run TestML on any project. We do not bill per seat or per run.

promise

Your tests, your code

Your test files stay with you. We do not collect them.

promise

Open spec

Read the spec, fork it, or port it to a new runtime. We invite that.

promise

Plain text

Tests are YAML-like text. You can audit them in any editor.

Clauses

01

Acceptance of terms

By cloning, installing, or running TestML, you agree to these terms. The rules apply to every user. They cover the source code, the spec, and the docs.

If you cannot accept the terms, do not use the project. Stop here. Uninstall the runtimes you pulled in.

02

Open-source license

TestML ships under an OSI-approved open-source license. You may use, copy, change, and share the code. No fee. No paywall. No vendor lock-in.

Forks and re-distributions must keep the license header intact. Strip nothing. Credit the project in your README or release notes.

03

Scope of the project

TestML is a test framework. It is not a CI runner. It is not a build tool. The project ships a YAML-like syntax for tests. It also ships runtimes for Python, JavaScript, Ruby, Perl, Java, and more.

We do not promise feature parity across every runtime. Each language port tracks the spec at its own pace. Check the runtime matrix in the docs before you ship.

04

No warranty

TestML is supplied as-is. We make no claim that it will fit your project. We make no claim that it is free of defects.

You run the tests at your own risk. The maintainers will not be liable for lost data, broken builds, or missed deadlines. Read the LICENSE file for the full legal text.

05

Acceptable use

Use TestML for lawful work. Do not use the project to build malware. Do not use it to attack systems you do not own.

Do not use the TestML name to claim a false partnership. The wordmark belongs to the project. Forks must rename themselves before they market a paid service.

06

Contributions

Pull requests follow the contributor guide in the repo. Sign the DCO line on each commit. By doing so, you grant the project a license to ship your patch under the same terms.

Code of conduct rules apply in every channel. Be kind. Stay on topic. Report abuse to the maintainers.

07

Third-party code

TestML depends on libraries from other authors. Their licenses bind you as well. Check each runtime's lock file for the full list.

If you embed TestML in a closed product, audit those licenses yourself. We track them, but you ship the build.

08

Marks and branding

The TestML name and logo are project marks. You may use them to refer to the framework in honest writing. You may not use them to brand a paid service that we did not endorse.

Ask first if you plan a t-shirt run, a conference talk track, or a paid course. Email the address at the foot of this page.

09

Termination

Break these rules and your right to use the project ends at once. You must remove the code from your systems.

These terms survive the end of your use. The warranty and trademark sections still bind you after that point.

10

Changes to these terms

We may revise these terms when the project changes. New text is dated in the meta strip above.

We will not e-mail every user. Watch the repo for diffs. Big shifts are also posted to the blog.

11

Governing law

These terms are read under the laws of the project's home jurisdiction. Disputes go to the courts of that jurisdiction first.

Nothing in this section blocks a user's local consumer rights. Read your local rules as well.

12

Contact and disputes

Reach the maintainers at contact@testml.org for legal queries. Use the GitHub issue tracker for bugs and feature work.

We aim to reply to legal mail within ten working days. Bug reports follow the triage cadence in the docs.

// Questions or disputes

Reach a maintainer before you file a claim

Most issues clear up over e-mail. Write to the address on the right. We aim to reply in ten working days. Bugs and feature work belong in the public tracker.