fix: apply clang-format to all source files
Fixes formatting violations that were causing CI failures. Applied clang-format-14 to ensure consistent code formatting across the codebase. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
@@ -62,6 +62,9 @@ Based on the directory structure, tests fall into the following categories:
|
||||
|
||||
## 3. Running Tests
|
||||
|
||||
> 💡 Need a refresher on presets/commands? See the [Build & Test Quick Reference](../build/quick-reference.md)
|
||||
> for the canonical `cmake`, `ctest`, and helper script usage before running the commands below.
|
||||
|
||||
### Using the Enhanced Test Runner (`yaze_test`)
|
||||
|
||||
The most flexible way to run tests is by using the `yaze_test` executable directly. It provides flags to filter tests by category, which is ideal for development and AI agent workflows.
|
||||
@@ -147,4 +150,4 @@ To run E2E tests and see the GUI interactions, use the `--show-gui` flag.
|
||||
|
||||
The GUI testing framework is designed for AI agent automation. All major UI elements are registered with stable IDs, allowing an agent to "discover" and interact with them programmatically via the `z3ed` CLI.
|
||||
|
||||
Refer to the `z3ed` agent guide for details on using commands like `z3ed gui discover`, `z3ed gui click`, and `z3ed agent test replay`.
|
||||
Refer to the `z3ed` agent guide for details on using commands like `z3ed gui discover`, `z3ed gui click`, and `z3ed agent test replay`.
|
||||
|
||||
Reference in New Issue
Block a user