🧪 test: verify lerp snapping in AsyncButtonTheme when parameter is not null - #11
Conversation
Co-authored-by: esenmx <43244505+esenmx@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. |
Replace three byte-identical check blocks (t=0.4/0.5/0.6) with one loop over (t, expected) records; failures now name the t value via `because`. Per-field `has(...)` checks are kept so the test stays independent of `operator==`. Header comment restores the "no-op" descriptor and ties the two transition builders to the loading-builder rationale. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1 participant
🎯 What: Added tests for
AsyncButtonTheme.lerpwhenotheris non-null.📊 Coverage: Verified that
loadingBuilderandtransitionBuildersnap fromfromtotoatt >= 0.5, testing att=0.4,t=0.5, andt=0.6.✨ Result: Comprehensive test coverage for theme lerping behavior and snapping point.
PR created automatically by Jules for task 2105429329520777024 started by @esenmx