// Use when: running or writing atframe_utils unit tests with the private test framework, filtering cases, or fixing Windows DLL/PATH test startup issues.
Use when: auditing or optimizing AI agent prompts, bridge files, skills, SKILL.md metadata, and cross-tool compatibility.
Use when: configuring or building atframe_utils with CMake, enabling samples/tests/tools, or selecting crypto/unwind backends.
| name | testing |
| description | Use when: running or writing atframe_utils unit tests with the private test framework, filtering cases, or fixing Windows DLL/PATH test startup issues. |
This repo uses a private unit testing framework (not GoogleTest). The framework is located in test/frame/.
The test executable is atframe_utils_unit_test.
Common commands:
./atframe_utils_unit_test./atframe_utils_unit_test -l / ./atframe_utils_unit_test --list-tests./atframe_utils_unit_test -r <group> or ./atframe_utils_unit_test -r <group>.<case>./atframe_utils_unit_test -f "pattern*" / ./atframe_utils_unit_test --filter "pattern*"./atframe_utils_unit_test -h, ./atframe_utils_unit_test -vOn Windows, running atframe_utils_unit_test.exe (or samples/tools) from a build directory may fail if dependent DLLs are not discoverable.
Preferred approach: prepend those folders to PATH for the current session.
Typical DLL directories in the monorepo/toolset layout:
<BUILD_DIR>\\publish\\bin\\<Config><REPO_ROOT>\\third_party\\install\\windows-amd64-msvc-19\\binExample (PowerShell):
$buildDir = "<BUILD_DIR>"$cfg = "Debug"$env:PATH = "$buildDir\\publish\\bin\\$cfg;$buildDir\\publish\\bin;${PWD}\\third_party\\install\\windows-amd64-msvc-19\\bin;" + $env:PATHSet-Location "$buildDir\\_deps\\atframe_utils\\test\\$cfg"./atframe_utils_unit_test.exe -r test_managerTest files are under test/case/.
Minimal example:
frame/test_macros.hCASE_TEST(group, case) and CASE_EXPECT_* assertions