What is xmake-unit-tests?

A guide for running and writing the internal tests of the xmake build tool itself. Xmake is a tool that builds C and C++ projects, while this skill focuses on testing xmake’s own source code.

Use it when fixing xmake, adding an xmake API, or checking a backport. It covers tests under xmake’s tests directory and their test runners.

It prevents confusion between testing xmake and testing a project that merely uses xmake. It provides the expected setup and commands for running the project’s test suite or a selected test.

xmake-unit-tests — Skill for Claude Code by xmake-io

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add xmake-io/xmake-skills --skill xmake-unit-tests

Clone the repo

git clone --depth 1 https://github.com/xmake-io/xmake-skills

Made for: Claude Code.

Or install xmake-skills, the plugin that ships this one along with the rest of its 58 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-unit-tests/github.svg)](https://agentmods.dev/skills/xmake-io/xmake-skills/xmake-unit-tests)

Your own site

<a href="https://agentmods.dev/skills/xmake-io/xmake-skills/xmake-unit-tests"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-unit-tests/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/xmake-io/xmake-skills/xmake-unit-tests"><img src="https://agentmods.dev/badge/skills/xmake-io/xmake-skills/xmake-unit-tests.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,604 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00078	$0.01604
Opus 5	$0.00039	$0.00802
Sonnet 5	$0.00016	$0.00321
Haiku 4.5	$0.00008	$0.00160

Measured 10d ago against content hash cf159b6ea0f4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

xmake-unit-tests scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 10d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/testing/xmake-unit-tests/SKILL.md · 161 lines

How it starts

The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Running & Writing Xmake's Unit Tests

This skill is about the xmake project's own internal test suite — useful when you are fixing a bug in xmake itself, adding a new API, or verifying a backport. For testing your own C/C++ project, see xmake-tests.

The suite lives under tests/ in the xmake source tree. Each subdirectory is a self-contained test (usually a mini project) driven by a runner.lua or a test.lua.

Prerequisites

You need a checkout of xmake and the source-level env loaded:

git clone --recursive https://github.com/xmake-io/xmake.git
cd xmake
./configure && make -j            # or on Windows: cd core && xmake
source scripts/srcenv.profile     # so `xmake` points at the local checkout
xmake l xmake.programdir          # verify: should end in .../xmake/xmake

See xmake-dev for the full build-from-source flow.

Run the whole suite

xmake l tests/run.lua

Iterates every subdirectory under tests/ that contains a runner.lua and runs it. Expect a scroll of "pass/skip" output.

Run a single test or group

xmake l tests/run.lua actions/build
xmake l tests/run.lua apis/add_files
xmake l tests/run.lua modules/lib_detect_find_tool
xmake l tests/run.lua plugins/project
xmake l tests/run.lua projects/c/console

The argument is a relative path under tests/. Any sub-tree works:

actions/ — tests for xmake build, xmake run, etc.
apis/ — per-API tests (add_files, add_defines, target:add, …)
modules/ — library module tests (lib.detect.find_tool, net.http, …)
plugins/ — plugin tests (project generator, doxygen, …)
projects/ — end-to-end mini projects per language
cli/ — CLI flag tests
benchmarks/ — performance benchmarks

Verbose and diagnosis

xmake l -vD tests/run.lua actions/build

-v shows each sub-command the test runs; -D dumps a Lua traceback on failure. Use this whenever a test fails — the default output is terse.

Layout of a single test

Read the full file on GitHub · 161 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

10d ago First seen · 161 lines · 78 tokens per session scan A cf159b6ea0f4

Subscribe to this mod's changes

xmake-unit-tests is a skill published in the GitHub repository xmake-io/xmake-skills (24 stars, last pushed 17d ago), licensed Apache-2.0. It adds 78 tokens to every session and 1,604 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Testing Unit testing

migrate-xunit-to-xunit-v3

Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…

dotnet/skills · 149 tokens

go-testing

Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.

Gentleman-Programming/gentle-ai · 26 tokens

nw-fp-clojure

Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.

nWave-ai/nWave · 25 tokens

mobiai-ios-testing

Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.

ArisGuimera/MobiAI-Core · 31 tokens

restore-internals-seams-in-finally-blocks-after-each-test

When delegating a task affected by this skill, include.

ZaxbyHub/opencode-swarm · 26 tokens

testing-llm

LLM and AI testing patterns — mock responses, evaluation with DeepEval/RAGAS, structured output validation, and agentic test patterns (generator, healer, planner). Use when testing AI features, validating LLM outputs, or building evaluation pipelines.

yonatangross/orchestkit · 55 tokens