메뉴
Denigma repository test harness conventions. Use when building Denigma, running Denigma tests, interpreting Denigma test failures, or choosing the correct working directory for the test executable.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Denigma classifier design conventions. Use when creating, editing, reviewing, or refactoring classifiers in src/classify or shared classification helpers used by exporters.
Denigma C++ namespace style. Use when adding, editing, reviewing, or refactoring C++ namespace declarations in this repository.
Denigma Windows compatibility convention for standard min/max calls. Use when adding, reviewing, or modifying any C++ code that calls std::min, std::max, std::clamp, numeric_limits<T>::min/max, or related standard-library min/max functions or members.
Denigma exporter enum mapping conventions. Use when adding, moving, reviewing, or modifying enum conversions for exporters such as MusicXML, MNX, MSS, SVG, or other format-specific code.
Denigma std::optional usage conventions. Use when adding, reviewing, or modifying std::optional fields or return values, especially for enum or bool state.
| name | denigma-test-harness |
| description | Denigma repository test harness conventions. Use when building Denigma, running Denigma tests, interpreting Denigma test failures, or choosing the correct working directory for the test executable. |
Run the test executable from tests/data, not from the repository root.
The GoogleTest binary expects the current working directory basename to be data and resolves inputs/outputs relative to that directory. Running it from the repository root causes broad false failures such as missing input files, Unknown or misplaced option: --mnx, or assertions from tests/denigmatests.cpp that the cwd is not data.
In tests that read fixtures or write generated outputs, call setupTestDataPaths(); at the start of the test to initialize the fixture and output paths consistently.
Preferred commands:
cmake --build build
../../build/tests/denigma_tests
Run the second command with working directory:
tests/data
ctest --test-dir build may report no registered tests even when build/tests/denigma_tests exists, so run the executable directly unless CTest registration has been verified.