Files
doormile_customer_app/test/sheet_stability_test.dart
Thiru-tenext 8427824951 A launch that opens in brand, and a sheet that stops resizing
── The splash, in three beats ──

Crimson edge to edge with the truck running across it in white; the invert;
then the mark.

The red starts before Flutter does. Four surfaces painted white before any
Dart runs — launch_background at both API levels, windowSplashScreenBackground
on Android 12+ in light and dark, and the iOS launch storyboard — and leaving
any one of them white makes the launch a white flash followed by a red one.
That flash is the only part of a launch a customer consciously notices.

The invert is one gesture rather than a fade. A white truck on a background
turning white is an invisible truck, so the ground lightens as the truck
darkens, off one controller, and the screen turns itself inside out with the
truck still on it. Fading it would have left the screen empty for the moment
before the mark.

The truck's colour is no longer its own: it is painted through srcIn, so the
file's palette is discarded and only alpha survives. A replacement Lottie now
needs no preparation, and tool/lottie_brand.py is off this path.

`splash.json` is a seamless 3.9s loop — frame 0 is frame 60, the truck never
arrives or departs — so there is no completion to hand over on. _truckBeat is
a decision about how long a launch may hold somebody, not a property of the
file. The comment claiming six seconds was wrong on both counts.

── Three things the splash was getting wrong quietly ──

It showed the wrong logo: doormile-icon.png, the previous mark, to a customer
who had just tapped the new one. tool/icons.py now cuts doormile-mark.png from
the same master alpha as the launcher icon, so they cannot drift again.

The fallback loader was invisible on red. _RoadLoader painted in DmColors.brand
on what used to be a white screen; on crimson that is crimson on crimson, and
it drew nothing at all on exactly the devices that had fallen back to it.

The mark appeared and left in the same frame — _minimum was the sum of the
beats exactly, so the clock ran out as the entrance finished. Hence _markHold.

── The truck was not in the middle ──

Not a layout bug: both beats sit in a Center and always did. The artwork is
drawn low and to the right inside its own 500x500 composition, so a centred
widget rendered an off-centre picture — 30pt right, 36pt down.

splash_centring_test.dart renders a frame at phone size and density, finds the
ink and fails if either beat drifts. It is the only form of test that could
have caught this, and the one that will catch it again when the Lottie is
replaced, which is when the correction goes stale. Two things it taught:
one enormous pump does not let the splash's async start-up chain advance, and
capturing at pixelRatio 1 rasterizes the speed lines too faintly to detect,
which truncates the bounding box and moves the measured centre by 12pt.

── The destination sheet stops resizing ──

Tapping ONE TOUCH opened a tall sheet that snapped shorter a few frames later.
DmAsyncList renders four skeleton rows while it loads — 302pt — and the states
that replace them are nearer 200; the sheet was Flexible, so it was as tall as
whichever state its content happened to be in, and the modal is still
animating up while that swap happens.

The list now lives in a box of one height. That also removes a second resize:
the sheet grew from 48% of the screen to 74% when a state was picked. Both
steps now measure 64% and it never changes size again.

And DmAsyncList takes initialItems, fed by AppState.cachedCities: FutureBuilder
reports `waiting` on its first build even for an already-complete future, so a
warm cache still flashed a skeleton over data it already had.

Three skeleton rows here rather than four — sheet_stability_test caught that
302pt overflows the smallest box the clamp can produce.
2026-09-28 12:54:03 +05:30

141 lines
4.9 KiB
Dart

import 'dart:async';
import 'package:flutter/material.dart';
import 'package:flutter_test/flutter_test.dart';
import 'package:doormile_cx/ui/widgets/states.dart';
/// ─────────────────────────────────────────────────────────────────────────
/// A SHEET DOES NOT CHANGE SIZE WHILE IT IS OPENING
///
/// Tapping ONE TOUCH opened a tall sheet that snapped shorter a few frames
/// later. Nothing was wrong with either height — the sheet was simply as tall
/// as whatever [DmAsyncList] happened to be rendering, and that changes twice
/// before the customer has done anything: four skeleton rows at 302pt, then
/// the states, which are nearer 200.
///
/// The modal is still animating up while that swap happens, so the resize is
/// not a subtle reflow. It is the first thing the customer sees.
///
/// Both halves of the fix are held here: the box the list lives in keeps one
/// height across every state the list can be in, and a list handed cached
/// items renders them on the first frame instead of a skeleton over data it
/// already has.
/// ─────────────────────────────────────────────────────────────────────────
void main() {
Widget host(Widget child) => MaterialApp(
home: Scaffold(
body: Center(
child: SizedBox(width: 360, child: child),
),
),
);
/// A load that never finishes, so the widget stays in its loading state.
Future<List<String>> never({bool refresh = false}) =>
Completer<List<String>>().future;
group('a fixed box holds its height', () {
testWidgets('loading and loaded measure the same', (tester) async {
const box = 300.0;
await tester.pumpWidget(
host(
SizedBox(
height: box,
child: DmAsyncList<String>(
skeletonRows: 3,
load: never,
emptyTitle: 'none',
emptyMessage: 'none',
builder: (_, items) => Column(children: [for (final i in items) Text(i)]),
),
),
),
);
await tester.pump();
final loading = tester.getSize(find.byType(DmAsyncList<String>));
await tester.pumpWidget(
host(
SizedBox(
height: box,
child: DmAsyncList<String>(
skeletonRows: 3,
initialItems: const ['Tamil Nadu'],
load: never,
emptyTitle: 'none',
emptyMessage: 'none',
builder: (_, items) => Column(children: [for (final i in items) Text(i)]),
),
),
),
);
await tester.pump();
final loaded = tester.getSize(find.byType(DmAsyncList<String>));
expect(loaded, loading, reason: 'the sheet would resize as it opened');
expect(loading.height, box);
});
testWidgets('three skeleton rows fit the smallest box the clamp allows', (
tester,
) async {
// The destination sheet floors its list box at 240. Four rows are 302 and
// overflowed it, which is why that sheet asks for three.
await tester.pumpWidget(
host(const SizedBox(height: 240, child: DmSkeleton(rows: 3))),
);
await tester.pump();
expect(tester.takeException(), isNull);
});
});
group('cached items skip the skeleton', () {
testWidgets('the first frame is the content, not a shimmer', (
tester,
) async {
await tester.pumpWidget(
host(
SizedBox(
height: 300,
child: DmAsyncList<String>(
initialItems: const ['Kerala'],
load: never,
emptyTitle: 'none',
emptyMessage: 'none',
builder: (_, items) =>
Column(children: [for (final i in items) Text(i)]),
),
),
),
);
// No settle, no extra pump: this is the frame the sheet opens on.
expect(find.text('Kerala'), findsOneWidget);
expect(find.byType(DmSkeleton), findsNothing);
});
testWidgets('without them it still loads honestly', (tester) async {
await tester.pumpWidget(
host(
SizedBox(
height: 300,
child: DmAsyncList<String>(
// Three for the same reason the destination sheet asks for
// three: the default of four is 302pt and does not fit here.
skeletonRows: 3,
load: never,
emptyTitle: 'none',
emptyMessage: 'none',
builder: (_, items) =>
Column(children: [for (final i in items) Text(i)]),
),
),
),
);
await tester.pump();
expect(find.byType(DmSkeleton), findsOneWidget);
});
});
}