🧪 Add widget tests for MainLayout#7
Conversation
- Added `screens` parameter to `MainLayout` to allow injecting simple mock screens during testing. - Created `test/screens/main_layout_test.dart` to verify that tapping bottom navigation items updates the current screen index correctly. - Added `mocktail` to `dev_dependencies` in `pubspec.yaml` for potential future mocking needs. Co-authored-by: hexamh <264230460+hexamh@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. |
1 participant
🎯 What: The testing gap addressed was missing widget tests for
MainLayout. The app's bottom navigation was untested.📊 Coverage: The scenarios now tested include the initial load (index 0) and the interactions of tapping each of the 5 bottom navigation items, verifying that the
IndexedStackcorrectly updates its index. To accomplish this cleanly without having to mock the 5 native plugins used by the real child screens,MainLayoutwas refactored slightly to accept an optionalscreensparameter to allow injecting simpleContainerwidgets during testing.✨ Result: The improvement in test coverage guarantees the app's main navigation structure won't silently break during refactors.
PR created automatically by Jules for task 3144498160761973520 started by @hexamh