test: Add WASM text metric update coverage (R3.46)#1238
Conversation
Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This PR adds unit test coverage for the WASM-side
update_text_metricsAPI, fulfilling requirement R3.46.What
tool_update_text_metrics_updates_boundstool_update_text_metrics_ignores_non_text_nodestool_update_text_metrics_with_max_widthtool_update_text_metrics_with_parent_manageddocs/REQUIREMENTS.mdtest matrix to reflect coverage.Why
To improve test coverage for the WASM API bridge and satisfy the requirement R3.46 which was previously untested directly.
Impact
Improves confidence in the text measuring logic within the WASM module without changing actual behavior.
Measurement
Run
cargo test --workspaceto execute the newly added 4 unit tests.PR created automatically by Jules for task 8318446655495389111 started by @khangnghiem