mockingjay
Ein Paket, das das Mocken, Testen und Überprüfen der Navigation in Flutter vereinfacht. Erstellt von Very Good Ventures 🦄
- Sterne
- 116
- Forks
- 11
- Letzter Push (UTC)
- 14.04.2026
- Projektstatus
- Archiviert
Original-README
Englischer Projektschnappschuss. Aktuelle Inhalte auf GitHub.
🕊 mockingjay
Developed with 💙 by Very Good Ventures 🦄
⚠️ This package is deprecated and no longer actively maintained.
The Flutter ecosystem has shifted toward Navigator 2.0 and declarative routing solutions such as
go_router. Mockingjay, which targets Navigator 1.0 APIs, no longer aligns with the direction of the ecosystem.The repository remains public and available to fork. For full migration guidance, see DEPRECATION.md.
A package that makes it easy to mock, test and verify navigation calls in Flutter. It works in tandem with mocktail, allowing you to mock a navigator the same way you would any other object, making it easier to test navigation behavior independently from the UI it's supposed to render.
Usage
To use the package in your tests, install it via dart pub add:
dart pub add dev:mockingjay
Then, in your tests, create a MockNavigator class like so:
import 'package:mockingjay/mockingjay.dart';
final navigator = MockNavigator();
Now you can create a new MockNavigator and pass it to a MockNavigatorProvider.
Any widget looking up the nearest Navigator.of(context) from that point will now receive the MockNavigator, allowing you to mock (using when) and verify any navigation calls. Use the included matchers to more easily match specific route names and types.
Note: make sure the MockNavigatorProvider is constructed below the MaterialApp. Otherwise, any Navigator.of(context) call will return a real NavigatorState instead of the mock.
Example
import 'package:flutter/material.dart';
import 'package:flutter_test/flutter_test.dart';
import 'package:mockingjay/mockingjay.dart';
class MyHomePage extends StatelessWidget {
const MyHomePage({super.key});
@override
Widget build(BuildContext context) {
return Scaffold(
body: TextButton(
onPressed: () => Navigator.of(context).push(MySettingsPage.route()),
child: const Text('Navigate'),
),
);
}
}
class MySettingsPage extends StatelessWidget {
const MySettingsPage({super.key});
static Route<void> route() {
return MaterialPageRoute(
builder: (_) => const MySettingsPage(),
settings: const RouteSettings(name: '/settings'),
);
}
@override
Widget build(BuildContext context) {
return const Scaffold();
}
}
void main() {
testWidgets('pushes SettingsPage when TextButton is tapped', (tester) async {
final navigator = MockNavigator();
when(navigator.canPop).thenReturn(true);
when(() => navigator.push<void>(any())).thenAnswer((_) async {});
await tester.pumpWidget(
MaterialApp(
home: MockNavigatorProvider(
navigator: navigator,
child: const MyHomePage(),
),
),
);
await tester.tap(find.byType(TextButton));
verify(
() => navigator.push<void>(
any(
that: isRoute<void>(
whereName: equals('/settings'),
),
),
),
).called(1);
});
}
Kategorien
Verwendete Abhängigkeiten
Abhängigkeiten 6 Einträge
- flutter
{"sdk":"flutter"} - flutter_test
{"sdk":"flutter"} - matcher
^0.12.17 - mocktail
^1.0.4 - test
^1.26.3 - very_good_analysisEntwicklung
^10.0.0
Wie wähle ich ein passendes Repository?
Nach Anwendungsfall filtern, Aktivität vergleichen und vor der Nutzung das Originalprojekt prüfen.
- Nach Name, Autor oder Beschreibung suchen und nach Thema eingrenzen.
- Sterne, Forks und letzte Pushes vergleichen. Sterne zeigen Interesse, garantieren aber keine Qualität.
- Vor der Nutzung README, Lizenz und Issues auf GitHub prüfen.
Quellen und Pflege
“A repository is the most basic element of GitHub.”
GitHub Docs — About repositories ↗
- VeryGoodOpenSource/mockingjay · GitHub ↗
- GitHub Docs — Saving repositories with stars ↗
- Verzeichnis gepflegt von Ducafecat ↗

