Runs CTest and publishes JUnit results to Jenkins. Supports both preset-based testing (from CMakePresets.json) and manual CTest invocation using the build context.

With presets:

stages {
    git.sync()
    cmake.build()
    cmake.test()
    // ...
}

Standalone (test preset configures and builds automatically if needed):

stages {
    git.sync()
    cmake.test()
    // ...
}

When CMakePresets.json contains testPresets:

When no test presets are found, cmake.test() uses the build context from cmake.build(). No additional parameters are added.

Note: In manual mode, cmake.test() requires cmake.build() to run first so it can read the build directory and configuration from context.

1. Looks up the test preset's configurePreset in CMakePresets.json
2. If the test preset's configure preset differs from the build preset's configure preset, automatically runs configure + build for the test configuration
3. Runs ctest --preset <preset> --output-on-failure --output-junit <results>
4. Publishes JUnit XML results to Jenkins
5. Marks the build as UNSTABLE if any tests fail

1. Reads ctx.cmakeBuildDir and ctx.buildConfig from the build stage context
2. Runs ctest -C <config> --output-on-failure --output-junit <results> in the build directory
3. Publishes JUnit XML results to Jenkins
4. Marks the build as UNSTABLE if any tests fail

When a test preset references a different configurePreset than what was used during cmake.build(), the test stage automatically runs its own configure + build step before testing. This allows test-specific configurations (e.g., with sanitizers or coverage flags) without affecting the main build.