Skip to main content

ogoron heal

Purpose​

Use ogoron heal to run tests and produce failure-focused artifacts that support test maintenance.

Subcommands​

  • ogoron heal tests — run tests and produce a heal issues report
  • ogoron heal ui-tests — run generated UI tests and produce a UI-focused healing workflow
  • ogoron heal conflicts — apply human verdicts from the latest heal_conflicts.xml and attempt automated fixes for eligible issues

Common options​

Common flags for ogoron heal tests:

  • --all — run all generated batches (not only the latest timestamp)
  • --project — run project tests from configuration (instead of generated tests)
  • --profile / --stack / --sut-preset — control test execution settings

Common flags for ogoron heal ui-tests:

  • --target — limit healing to one generated UI test file or subdirectory inside .ogoron/tests/tests/ui/generated

Outputs​

Healing workflows write:

  • human-friendly reports under .ogoron/for-human/
  • private run evidence under .ogoron/.meta/

Examples​

# Run tests and build a heal report
ogoron heal tests

# Run generated UI tests and build a UI heal workflow
ogoron heal ui-tests

# Apply human verdicts and attempt automated fixes for eligible issues
ogoron heal conflicts

Notes​

  • Healing requires that tests can be executed for your stack and environment. Stack-specific requirements are documented separately.
  • ogoron heal ui-tests operates on the UI workspace under .ogoron/tests.
  • Use ogoron heal --help to see flags like selection mode and execution profile options.