feat(checks): opt-in progress logging for scenario/check execution (#…

[demoiverrakada]

…2421)

Description

Adds opt-in, per-step progress logging to the scenario runner so long Suite.run()
executions surface which scenario and checks are running — useful in CI, scripts, and
notebooks where the rich progress bar doesn't render.

Suite.run() already exposes a verbose flag + _SuiteProgress bar for scenario-level
progress; this closes the check-level gap, where ScenarioRunner._run_once previously
emitted nothing.

Changes

• scenarios/runner.py: module logger; INFO logs at step start (scenario name + step
  index + check identities) and completion (pass/fail). check.name falls back to
  check.kind when unset.
• tests/scenarios/test_runner_logging.py: covers logs-at-INFO and quiet-by-default.

Design

• Opt-in via standard logging levels — silent by default; enable with
  logging.getLogger("giskard").setLevel(logging.INFO). No new API, backward-compatible
  (uses the Python-logging option suggested in the issue).
• Async-safe — every log line includes the scenario name, so interleaved output under
  parallel=True stays readable.
• Scenario-level rich bar left untouched.

Testing — full giskard-checks suite (754 passed), whole monorepo (1,268 passed,
0 failed), serial + parallel=True verified manually, make check clean.

Developed with AI assistance (human-in-the-loop; I reviewed and verified all changes).

Related Issue

Type of Change

• 📚 Examples / docs / tutorials / dependencies update
• 🔧 Bug fix (non-breaking change which fixes an issue)
• [x ] 🥂 Improvement (non-breaking change which improves an existing feature)
• 🚀 New feature (non-breaking change which adds functionality)
• 💥 Breaking change (fix or feature that would cause existing functionality to change)
• 🔐 Security fix

Coding agents

Autonomous agents with no human in the loop must read AUTONOMOUS.md before opening a PR.

PR title: agent-opened PRs must end the title with 🤖🤖🤖🤖 (exactly four robot emojis). Do not omit — that suffix is how the expedited agent PR workflow picks up the PR.

Checklist

• [ x] I've read the CODE_OF_CONDUCT.md document.
• [ x] I've read the CONTRIBUTING.md guide.
• [ x] I've written tests for all new methods and classes that I created.
• I've written the docstring in NumPy format for all the methods and classes that I created or modified.
• I've updated the uv.lock running uv lock (only applicable when pyproject.toml has been
  modified)

[gemini-code-assist]

Code Review

This pull request introduces opt-in progress logging at the INFO level for the scenario runner, allowing callers to track step-by-step execution and check status. It also adds a comprehensive test suite to verify this behavior and ensure backward compatibility. The feedback suggests wrapping the logging calls and string formatting inside if logger.isEnabledFor(logging.INFO): checks to prevent unnecessary overhead when logging is disabled.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[davidberenstein1957]

@demoiverrakada, thank for the contribution! Would you be able to resolve the conflict?

[davidberenstein1957]

Reviewed. Ready to merge pending CI.