تشغيل أي مهارة في Manus بنقرة واحدة

ابدأ الآن

test

النجوم٠

التفرعات٠

آخر تحديث١٣ مايو ٢٠٢٦ في ١٧:٤٤

Run the unit-test suite. Use to run, filter, or disable tests.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

SRombauts

SRombauts/pong-sdl3-cpp

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

محللو ضمان جودة البرمجيات والمختبرونمهن الحاسوب والرياضيات·SOC 15-1253

SKILL.md

readonly

name	test
description	Run the unit-test suite. Use to run, filter, or disable tests.

Test

Tests are built by default alongside the main executable, registered with CTest via doctest_discover_tests(). Build the project first (see the build skill); the test scripts deliberately do not trigger a build.

Run all tests

scripts\test.ps1

./scripts/test.sh

Both default to Debug (-Config Release / --config Release to override). Raw fallback:

ctest --test-dir build --output-on-failure

Run an individual test target or case

Filter via CTest (regex over registered test names):

ctest --test-dir build -R smoke --output-on-failure

Or invoke the test executable directly with doctest filters:

Linux/macOS: build/pong-sdl3-cpp-tests -tc=smoke
Windows (Visual Studio generator): build\tests\Debug\pong-sdl3-cpp-tests.exe -tc=smoke

Disable testing entirely

Pass -DBUILD_TESTING=OFF at configure time. CMake's standard option (set by include(CTest)); skips both the test target and the FetchContent download of doctest:

cmake -S . -B build -DBUILD_TESTING=OFF

In this configuration scripts/test.{ps1,sh} will exit non-zero with "No tests were found": the wrappers pass --no-tests=error to CTest so a build without a test target fails loudly instead of silently reporting "Tests passed" on zero discovered tests. To opt out (e.g. a sanity-check run on a BUILD_TESTING=OFF build), forward --no-tests=ignore:

scripts\test.ps1 -ExtraArgs '--no-tests=ignore'

./scripts/test.sh -- --no-tests=ignore

Rules

Always build before running tests; the scripts fail fast if build/ does not exist.
Add new tests under tests/<TypeName>Test.cpp (CamelCase, mirroring the type or area being tested) and let doctest_discover_tests() pick them up; do not edit CTest registration by hand.
A non-zero exit from CTest means a real failure — surface it rather than re-running blindly. "No tests were found" is one such failure: it usually means the build was configured with BUILD_TESTING=OFF, or the test target was never built into the current build/ (partial / stale state). Re-run scripts/build.{ps1,sh} rather than retrying ctest.

المزيد من هذا المستودع

نفس المستودع

agent-response-style

SRombauts/pong-sdl3-cpp

Default response behavior for AI coding agents: professional, factual, neutral tone with calibrated critical evaluation. Baseline for every task — implementation, code review, debugging, planning, research, evaluation, Q&A.

2026-06-020

game-code-architecture

SRombauts/pong-sdl3-cpp

Design and review guidelines for this SDL3 Pong codebase: frame-loop constraints, testable layering, and design patterns. Use when designing new features, populating the ISSUES.md, implementing a task, reviewing a diff or branch, or when the user asks for an architecture or standards check.

2026-05-210

repo-conventions

SRombauts/pong-sdl3-cpp

Repository layout and naming conventions. Use to find or place files.

2026-05-210

development-workflow

SRombauts/pong-sdl3-cpp

Standard end-to-end workflow for working on a task in this repository: branch naming, implement + tests + style, self-review, commit, `docs/ISSUES.md` cleanup, push the branch, and open a PR with `gh`. Use when starting work on an entry from `docs/ISSUES.md` (or, when one is filed, a GitHub issue).

2026-05-200

format

SRombauts/pong-sdl3-cpp

Format and verify C/C++ source style with clang-format.

2026-05-160

build

SRombauts/pong-sdl3-cpp

Build the project. Use to build, compile, test, or run the project.

2026-05-090

name	test
description	Run the unit-test suite. Use to run, filter, or disable tests.

Test

Run all tests

scripts\test.ps1

./scripts/test.sh

Both default to Debug (-Config Release / --config Release to override). Raw fallback:

ctest --test-dir build --output-on-failure

Run an individual test target or case

Filter via CTest (regex over registered test names):

ctest --test-dir build -R smoke --output-on-failure

Or invoke the test executable directly with doctest filters:

Linux/macOS: build/pong-sdl3-cpp-tests -tc=smoke
Windows (Visual Studio generator): build\tests\Debug\pong-sdl3-cpp-tests.exe -tc=smoke

Disable testing entirely

Pass -DBUILD_TESTING=OFF at configure time. CMake's standard option (set by include(CTest)); skips both the test target and the FetchContent download of doctest:

cmake -S . -B build -DBUILD_TESTING=OFF

scripts\test.ps1 -ExtraArgs '--no-tests=ignore'

./scripts/test.sh -- --no-tests=ignore

Rules

Always build before running tests; the scripts fail fast if build/ does not exist.
Add new tests under tests/<TypeName>Test.cpp (CamelCase, mirroring the type or area being tested) and let doctest_discover_tests() pick them up; do not edit CTest registration by hand.
A non-zero exit from CTest means a real failure — surface it rather than re-running blindly. "No tests were found" is one such failure: it usually means the build was configured with BUILD_TESTING=OFF, or the test target was never built into the current build/ (partial / stale state). Re-run scripts/build.{ps1,sh} rather than retrying ctest.