fix(tests): coverage report NoSource failure on main

[ocervell]

Problem

The Tests workflow is red on main — the coverage job fails at Run coverage report (coverage combine --keep succeeds, then coverage report -m prints no table and exits 1). Introduced by #1267.

Root cause (reproduced locally):

No source for code: '/tmp/tmp8dwgpdlo/mydriver.py'; see .../messages.html#error-no-source
EXIT=1

#1267's tests/unit/test_runner_hooks.py dropped the fake driver into a system TemporaryDirectory and imported it as secator.hooks.mydriver. Coverage recorded that /tmp/... path. The unit job passed (it only writes coverage data), but the separate coverage job combines the unit+integration data and runs coverage report; by then the tempdir is gone, so coverage raises NoSource and exits 1. The path isn't caught by --omit=*/site-packages/*,*/tests/*,*/templates/*.

Fix

Mirror the existing tests/unit/test_loader.py convention: write the driver into the real CONFIG.dirs.templates dir (its path contains /templates/, so the report's --omit=*/templates/* excludes it) and clean it up in tearDownClass. No change to the runtime fix from #1267 — this only relocates where the test's throwaway driver file lives.

Verification

• coverage run … test_runner_hooks.py → 4 passed; then coverage report --omit=… → exit 0, full table, 0 "No source" errors (was exit 1 before).
• Driver file is removed after the run (no stray file left in ~/.secator/templates/).
• flake8 clean.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Tests
  • Updated hook-related test coverage to use a real external driver fixture during initialization.
  • Improved validation for custom hook registration, persistence after serialization, and repeated context application.

[coderabbitai]

Walkthrough

Test fixtures in tests/unit/test_runner_hooks.py were updated to load a custom external driver from the real CONFIG.dirs.templates directory rather than a temporary directory. The driver was renamed from mydriver to custom_hook_driver across setup, teardown, and test assertions.

Changes

Runner Hooks Test Fixture Migration

Layer / File(s)	Summary
Fixture setup/teardown and test references tests/unit/test_runner_hooks.py	Custom driver is now written to custom_hook_driver.py under the real templates directory, with discovery cache cleared/reset in setUpClass and file/module cleanup in tearDownClass; tests updated to reference custom_hook_driver instead of mydriver.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Poem

A rabbit hopped through templates true,
Swapped out "mydriver" for something new,
No tempdir tricks, just the real place,
Hooks still fire with steady grace. 🐇✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main change: fixing a test-related coverage report NoSource failure on main.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/coverage-report-nosource-tempdir

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}