원클릭으로 Manus에서 모든 스킬 실행

spice-test

스타86

포크5

업데이트2026년 5월 31일 23:53

Run the Spice `spicetest` suite (GoogleTest-based integration + unit tests). Use when the user wants to run all tests, a specific suite or case, update reference files, check for memory leaks with valgrind, or debug a failing test.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

spicelang

spicelang/spice

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

Run Spice tests

spicetest is a GoogleTest binary built from test/. It drives two kinds of tests:

Reference / integration tests parameterized over directories in test/test-files/<group>/.... Each test case dir has a source.spice plus reference files the runner compares against (see below).
Unit tests in test/unittest/ (e.g. BlockAllocatorTest, CommonUtilTest).

Build it first (see the spice-build skill): cmake --build cmake-build-debug --target spicetest.

The binary lands at cmake-build-debug/test/spicetest.

Running

# All tests
cmake-build-debug/test/spicetest

# List every test name (best way to find an exact filter)
cmake-build-debug/test/spicetest --gtest_list_tests

# Filter by suite or case (GoogleTest globbing)
cmake-build-debug/test/spicetest --gtest_filter='IRGeneratorTests*'
cmake-build-debug/test/spicetest --gtest_filter='CommonUtilTest.*'
cmake-build-debug/test/spicetest --gtest_filter='*ForLoop*'

Reference-test suites (instantiated from test/test-files/<group>): CommonTests, LexerTests, ParserTests, SymbolTableBuilderTests, TypeCheckerTests, IRGeneratorTests, StdTests, BenchmarkTests, ExampleTests, BootstrapCompilerTests.

Custom test-runner flags

These are spicetest's own flags (not GoogleTest):

--update-refs — regenerate/overwrite reference files from current output. Use after an intentional change to compiler output, then review the diff.
--run-benchmarks — also run benchmark cases and check baselines.
--leak-detection — wrap tests in valgrind to detect leaks.
--skip-sanitizer-tests — skip tests exercising language sanitizers.
--is-github-actions — skip cases unsupported on CI.
--verbose — extra runner debug output.

# Update refs for one suite after an intended change, then inspect git diff
cmake-build-debug/test/spicetest --gtest_filter='IRGeneratorTests*' --update-refs
git diff test/test-files

Memory-leak / debugging

# Valgrind on a focused set (full run is slow)
valgrind --leak-check=full cmake-build-debug/test/spicetest --gtest_filter='ParserTests*'

# Or the dedicated build target
cmake --build cmake-build-debug --target spicetest_leakcheck

# Debug a failing case under gdb
gdb --args cmake-build-debug/test/spicetest --gtest_filter='TypeCheckerTests*'

Reference files in a test-case directory

Common files the runner reads/compares (presence is optional per case):

source.spice (+ source1.spice, …) — input program
cout.out — expected stdout; exception.out / warning.out — expected errors/warnings
exit-code.out — expected process exit code
ir-code.ll, ir-code-O2.ll, ir-code-O3.ll, … — expected LLVM IR per opt level
assembly-linux-amd64.asm, assembly-linux-aarch64.asm — expected assembly
symbol-table.json, type-registry.out — expected symbol/type dumps
syntax-tree.dot / parse-tree.dot / dependency-graph.dot — expected graphs
Platform/skip markers: *-windows.*, *-macos.*, skip-windows, skip-gh-actions, run-builtin-tests, cli-flags.txt

To produce these dumps manually for a single input, use the spice-dump skill.

이 저장소의 다른 Skills

같은 저장소

spice-build

spicelang/spice

Build the Spice compiler (`spice`) and/or the test runner (`spicetest`) with CMake/Ninja. Use when the user wants to compile/rebuild the project, build a specific target, produce a release/debug build, or set up the CMake build directory before running or testing.

2026-06-2486

spice-contribute

spicelang/spice

Guidelines for contributing changes to the Spice GitHub repository — branch naming conventions, commit message format, PR workflow, no-push-to-main rule, and quality gates. Use when preparing a branch for review, writing a commit, opening a PR, or checking that a contribution is ready to merge.

2026-06-0786

spice-profiling

spicelang/spice

Profile and benchmark the Spice compiler (the host C++ `spice` program) and the native binaries it emits from `.spice` files — using the built-in per-stage timers, the dedicated CMake profiling build options, and external tools (perf, valgrind/callgrind, flamegraph, hyperfine). Covers the preferred build/compile settings for representative profiling of each layer. Use when the user wants to find where compile time or runtime is spent, benchmark a change, or chase a performance regression.

2026-06-0186

spice-debugging

spicelang/spice

Find, diagnose, and fix bugs in the Spice compiler or in a compiled Spice program using GDB, objdump, sanitizers (for both the host C++ compiler and the emitted Spice program via the built-in `--sanitizer` flag), the compiler dump flags, and valgrind. Use when investigating a crash, miscompilation, memory error, or undefined behavior, or when triaging a failing test. Whenever a bug is fixed, this skill also requires extending or adding a test that covers the problematic code path and any related uncovered paths.

2026-06-0186

spice-add-test

spicelang/spice

Add a reference/integration test case under test/test-files for the Spice compiler. Covers the directory layout (flat vs grouped suites), the exact reference filenames the runner compares against, control/skip marker files, platform-specific variants, and the --update-refs workflow to generate expected output. Use when adding or modifying compiler test cases.

2026-06-0186

spice-architecture

spicelang/spice

Orientation map of the Spice compiler codebase — the compilation pipeline (lexer → parser → CST → AST → import collector → symbol table → type checker → IR generator → optimizer → object emitter → linker), the key class/file for each stage, and the SourceFile orchestration sequence. Use when navigating the compiler, deciding where a change belongs, or understanding how a stage feeds the next.

2026-06-0186

name	spice-test
description	Run the Spice `spicetest` suite (GoogleTest-based integration + unit tests). Use when the user wants to run all tests, a specific suite or case, update reference files, check for memory leaks with valgrind, or debug a failing test.

Run Spice tests

spicetest is a GoogleTest binary built from test/. It drives two kinds of tests:

Reference / integration tests parameterized over directories in test/test-files/<group>/.... Each test case dir has a source.spice plus reference files the runner compares against (see below).
Unit tests in test/unittest/ (e.g. BlockAllocatorTest, CommonUtilTest).

Build it first (see the spice-build skill): cmake --build cmake-build-debug --target spicetest.

The binary lands at cmake-build-debug/test/spicetest.

Running

# All tests
cmake-build-debug/test/spicetest

# List every test name (best way to find an exact filter)
cmake-build-debug/test/spicetest --gtest_list_tests

# Filter by suite or case (GoogleTest globbing)
cmake-build-debug/test/spicetest --gtest_filter='IRGeneratorTests*'
cmake-build-debug/test/spicetest --gtest_filter='CommonUtilTest.*'
cmake-build-debug/test/spicetest --gtest_filter='*ForLoop*'

Custom test-runner flags

These are spicetest's own flags (not GoogleTest):

--update-refs — regenerate/overwrite reference files from current output. Use after an intentional change to compiler output, then review the diff.
--run-benchmarks — also run benchmark cases and check baselines.
--leak-detection — wrap tests in valgrind to detect leaks.
--skip-sanitizer-tests — skip tests exercising language sanitizers.
--is-github-actions — skip cases unsupported on CI.
--verbose — extra runner debug output.

# Update refs for one suite after an intended change, then inspect git diff
cmake-build-debug/test/spicetest --gtest_filter='IRGeneratorTests*' --update-refs
git diff test/test-files

Memory-leak / debugging

# Valgrind on a focused set (full run is slow)
valgrind --leak-check=full cmake-build-debug/test/spicetest --gtest_filter='ParserTests*'

# Or the dedicated build target
cmake --build cmake-build-debug --target spicetest_leakcheck

# Debug a failing case under gdb
gdb --args cmake-build-debug/test/spicetest --gtest_filter='TypeCheckerTests*'

Reference files in a test-case directory

Common files the runner reads/compares (presence is optional per case):

source.spice (+ source1.spice, …) — input program
cout.out — expected stdout; exception.out / warning.out — expected errors/warnings
exit-code.out — expected process exit code
ir-code.ll, ir-code-O2.ll, ir-code-O3.ll, … — expected LLVM IR per opt level
assembly-linux-amd64.asm, assembly-linux-aarch64.asm — expected assembly
symbol-table.json, type-registry.out — expected symbol/type dumps
syntax-tree.dot / parse-tree.dot / dependency-graph.dot — expected graphs
Platform/skip markers: *-windows.*, *-macos.*, skip-windows, skip-gh-actions, run-builtin-tests, cli-flags.txt

To produce these dumps manually for a single input, use the spice-dump skill.