zulip/zulip-flutter

tests: Get route-transition duration robustly, instead of hard-coding

Open

#1,668 opened on Jul 4, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Dart (456 forks)github user discovery
a-testshelp wanted

Repository metrics

Stars
 (454 stars)
PR merge metrics
 (PR metrics pending)

Description

When https://github.com/flutter/flutter/pull/171109 lands, we should use the new TransitionDurationObserver instead of hard-coding what we expect a transition duration to be, e.g. in code like this:

            // sheet appears onscreen; default duration of bottom-sheet enter animation
            await tester.pump(const Duration(milliseconds: 250));

Once that's the norm instead of the exception, we can close this issue.

Contributor guide

Research direction
Study the TransitionDurationObserver from the Flutter PR #171109, then locate all hard coded transition durations in zulip flutter's test files and replace them with the observer.
Tech stack
dartflutter
Domain
mobile
Issue type
Test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
DartFlutterTesting
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70