Add video step-overlay walkthrough report#247
Merged
Conversation
Up to standards ✅🟢 Issues
|
| Metric | Results |
|---|---|
| Complexity | 43 |
| Duplication | 0 |
NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Reporting batch — the visual companion to the HTML/JSON reports. Full layers + tests + EN/Zh v39 docs + README.
Feature (
utils/video_report, cv2 only on the real path)write_step_video(steps, output, fps, seconds_per_step): renders per-step screenshots into a walkthrough video where each frame is held for a few seconds with its caption and a pass/fail colour banner burned in.build_overlay_plan(per-step frame plan, no I/O) andrender_overlay_frame(single banner) are usable on their own.loader/drawer/writer_factoryhooks are injectable, so the assembly logic is unit-tested with fakes and nocv2/numpydependency (runs in quality.yml). The real path lazily importscv2only when those hooks are absent; a dedicated test exercises it underimportorskip. The writer is released in afinally.AC_write_step_video(steps as list or builder JSON string); MCPac_write_step_video; Builder under Report.Verification