FLUTTER ECOSYSTEM

VeryGoodOpenSource/mockingjay

Um pacote que facilita o mock, teste e verificação de navegação no Flutter. Criado pela Very Good Ventures 🦄

Capa do projeto mockingjay
Stars
116
Forks
11
Último push (UTC)
14 de abr. de 2026
Status do projeto
Arquivado
Very Good Open Source GitHub avatar
GITHUB Organization

Very Good Open Source ↗

Open source code from Very Good Ventures (@VGVentures)

New York, NYSite oficial ↗
LinguagensDartHTMLShellSwiftKotlinObjective-C

Tópicos técnicos

Dependências usadas

Lista de dependências 6 itens

README original

Texto original em inglês. Visite o GitHub para a versão atual.

Expandir / recolher README

🕊 mockingjay

Very Good Ventures Very Good Ventures

Developed with 💙 by Very Good Ventures 🦄

ci coverage pub package License: MIT style: very good analysis


⚠️ 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);
  });
}