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.

Unit testing (atframe_utils)

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:

Run all tests: ./atframe_utils_unit_test
List tests: ./atframe_utils_unit_test -l / ./atframe_utils_unit_test --list-tests
Run a group/case: ./atframe_utils_unit_test -r <group> or ./atframe_utils_unit_test -r <group>.<case>
Filter: ./atframe_utils_unit_test -f "pattern*" / ./atframe_utils_unit_test --filter "pattern*"
Help/version: ./atframe_utils_unit_test -h, ./atframe_utils_unit_test -v

On 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:

Example (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:PATH
Set-Location "$buildDir\\_deps\\atframe_utils\\test\\$cfg"
./atframe_utils_unit_test.exe -r test_manager

Test files are under test/case/.

Minimal example:

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.