migration-behavior-reporting

Behavior coverage reports translate migration test suites into reviewer-friendly, behavior-oriented scenarios describing observable outcomes. The skill updates the nextest-backed Markdown/HTML report pipeline to output human-readable summaries without requiring source code inspection.

Behavior-oriented migration scenarios are reviewer-facing test summaries describing observable outcomes rather than implementation details. You need them when maintaining accurate behavior coverage reports for citum-migrate to ensure published documentation matches underlying tests.

You keep migration test reports readable without slowing CI by scoping report publication to main-only or manual docs workflows. This regenerates reviewer-meaningful Markdown/HTML outputs via the migration-report script while avoiding CI-time increases.

Yes, nextest works with Markdown and HTML report generation by backing the migration behavior coverage report. The skill integrates suite-to-report mappings via specified scripts to emit concise repo-relative source references and update the published docs output path.

Yes, you can update the published docs output path for migration behavior reports. The skill maintains alignment between tests and the published report by updating the report generation pipeline and regenerating the output through the migration-report script.

The best way to convert implementation-focused migration tests is rewriting them into announce_behavior-style scenarios with human-readable names and bullet summaries. This ensures the nextest-backed report remains review-ready and concise without opening source files.