testing

Run Scene Optimizer C++ unit and Python binding tests via repo scripts.

31|4|Updated May 21, 2026
One-click install
npx skills add https://github.com/NVIDIA-Omniverse/usd-optimize --skill testing-nvidia-omniverse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/NVIDIA-Omniverse/usd-optimize/tree/main/.agents/skills/testing
Command: npx skills add https://github.com/NVIDIA-Omniverse/usd-optimize --skill testing-nvidia-omniverse

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures Scene Optimizer’s C++ unit tests and Python binding tests run consistently and that failures are caught early across build configurations and targeted test selection.

Core Features & Use Cases

  • Run All Tests: Execute the default C++ and Python test suites in one command.
  • Targeted Test Runs: Filter C++ doctest cases by name pattern and run specific Python test modules/classes/methods.
  • Build & Coverage Workflows: Run tests against debug or release builds, and perform Linux-only gcov coverage collection with HTML report generation.

Quick Start

Run the full default test run with:

  • ./repo.sh test

Frequently Asked Questions about testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run C++ unit tests and Python binding tests for stage optimization operations?

Run C++ unit tests and Python binding tests by invoking the repo wrapper scripts (repo.sh or repo.bat) with the test command, which executes the default test suites in one command rather than running test binaries directly.

Can I filter doctest cases by name pattern and run specific Python test modules?

Yes, you can execute targeted test runs by filtering C++ doctest cases by name pattern and specifying individual Python test modules, classes, or methods through the repo wrapper script suite selection options.

How do I collect gcov coverage data and generate HTML reports for C++ tests on Linux?

Collect gcov coverage data by running tests with the Linux-only coverage collection configuration through the repo wrapper script, which generates HTML reports alongside the test execution results.

Do I need to run test binaries directly to validate Scene Optimizer operations?

No, you should not run test binaries directly; instead, invoke the repo wrapper scripts (repo.sh/repo.bat) with correct suite selection, optional debug or release config switching, and deterministic environment setup to validate operations reliably.

Can I run unit tests against both debug and release build configurations?

Yes, you can run unit tests against either debug or release build configurations by applying optional config switching when invoking the repo wrapper script test command for deterministic execution.

Why does my pytest-style test discovery fail when running Scene Optimizer test suites?

Pytest-style test discovery may fail if you run test binaries directly instead of using the repo wrapper scripts with correct suite selection and deterministic environment setup required for reliable execution.