Pending timers in widget test when watching a table

[GP4cK]

Let's say I have a widget that watches a table:

class MyApp extends StatefulWidget {
  const MyApp(this.db, {super.key});
  final AppDatabase db;

  @override
  State<MyApp> createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {
  late final stream = widget.db.select(widget.db.todoItems).watch();

  @override
  Widget build(BuildContext context) {
    // ...
  }
}

If I test that widget like so:

void main() {
  late AppDatabase db;
  setUpAll(() {
    db = AppDatabase();
  });
  tearDownAll(() {
    db.close();
  });
  testWidgets('MyApp', (tester) async {
    await tester.pumpWidget(MyApp(db));
  });
}

I will get this error:

Pending timers:
Timer (duration: 0:00:00.000000, periodic: false), created:
#0      new FakeTimer._ (package:fake_async/fake_async.dart:308:62)
#1      FakeAsync._createTimer (package:fake_async/fake_async.dart:252:27)
#2      FakeAsync.run.<anonymous closure> (package:fake_async/fake_async.dart:185:19)
#6      StreamQueryStore.markAsClosed (package:drift/src/runtime/executor/stream_queries.dart:137:11)
#7      QueryStream._onCancelOrPause (package:drift/src/runtime/executor/stream_queries.dart:288:14)
#8      QueryStream._stream.<anonymous closure>.<anonymous closure> (package:drift/src/runtime/executor/stream_queries.dart:220:11)
#17     _StreamBuilderBaseState._unsubscribe (package:flutter/src/widgets/async.dart:149:22)
#18     _StreamBuilderBaseState.dispose (package:flutter/src/widgets/async.dart:124:5)
#19     StatefulElement.unmount (package:flutter/src/widgets/framework.dart:5696:11)
#20     _InactiveElements._unmount (package:flutter/src/widgets/framework.dart:2077:13)
...

The only way to fix it, is to move the db.close() inside the body of the testWidgets. But if the test fail for another reason, db.close() may never be called so I don't think it's great either...

Is there a better way of doing this?
Here's the link to a minimum reproducible example: https://github.com/GP4cK/drift_stream_timer_issue

[simolus3]

In the next drift version, you'll be able to use DatabaseConnection(NativeDatabase.memory(), closeStreamsSynchronously: true) to fix this issue.