flutter-testing
/flutter-testing
Pisze i uruchamia testy Fluttera: jednostkowe, dla Cubit i BLoC, repozytoriów, widgetów i integracyjne, zgodnie z konfiguracją projektu.
- Autor
- imdanishk ↗
- Repozytorium
- flutter-ai-kit ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 13.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Pisze i uruchamia testy Fluttera: jednostkowe, dla Cubit i BLoC, repozytoriów, widgetów i integracyjne, zgodnie z konfiguracją projektu.
Oryginalny opis (EN)
Writes and runs Flutter tests (unit, cubit or bloc, repository, widget, integration) following the project's existing test setup. Use ONLY when the developer explicitly asks for tests, test setup or a test run; never add tests to other tasks.
Jak działa
- Steps
- Rules
Podgląd SKILL.md
--- name: flutter-testing description: Writes and runs Flutter tests (unit, cubit or bloc, repository, widget, integration) following the project's existing test setup. Use ONLY when the developer explicitly asks for tests, test setup or a test run; never add tests to other tasks. license: Apache-2.0 --- # Flutter testing (on demand only) Do not use this skill unless the developer asked for tests in this request. Other skills never add tests on their own; if a task would benefit from tests, say so in one line and stop. ## Steps 1. **Read the project's test setup.** Look at `test/` and `integration_test/` (layout, naming, helpers), `dev_dependencies` in `pubspec.yaml` (`flutter_test`, `bloc_test`, `mocktail`, `mockito`, `patrol`, `integration_test`), the project profile and any testing rules in `AGENTS.md`. Copy what exists: the same mock library, the same folder mirror of `lib/`, the same helper functions. Where a project rule and this skill disagree, the project rule wins. 2. **If there is no test setup,** propose the smallest one and ask before adding a package: `flutter_test` (in the SDK) and `mocktail`; plus `bloc_test` when the project uses Cubit or Bloc. Do not add a coverage tool, golden-test tool or UI driver unless asked. 3. **Agree on scope in one line** (which classes, which layer, which cases) when the request is broad. Default order of value: state classes (cubit, bloc or notifier) including the error path; repositories with the data source mocked; then one widget test per page that shows loading, data and error. Integration tests only when asked, and say they are slower and need a device or emulator. 4. **Write the tests** from `references/patterns.md`: test behaviour (what state sequence results from an action), not implementation details; one reason to fail per test; mock only the edges (repository, data source, clock). Do not test generated files (`*.g.dart`, `*.freezed.dart`, `*.gr.dart`) or plain data classes. 5. **Run them,** with the `fvm` prefix when `.fvmrc` exists: `flutter test test/path_test.dart` for the files you wrote, then the whole `flutter test` if time allows. Report the result as it is. If the run cannot happen (no SDK in the environment, missing generated files or secrets), say what was not run. 6. **When a test fails,** find out whether the test or the app code is wrong. Never weaken or delete a test to make it pass. If the app code has a bug, report it with the file and line and ask before changing app code that is outside the request. 7. **Finish** with: files added, what each covers, what is deliberately not covered, the command to run them, and the result. ## Rules - Never put real keys, tokens or personal data in tests or fixtures. - Do not make tests depend on the network, the clock, random values or the order other tests run in. - A new test package changes `pubspec.yaml`: that is a package addition, so ask first. - Android and iOS differences matter only for integration tests and plugins: plugin calls in unit tests need mocks of the platform channel or the plugin's interface; see Flutter's "Plugins in Flutter tests" page.
Pliki w paczce (2)
- SKILL.md 3 KB
- references/patterns.md 5 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · imdanishk/flutter-ai-kit | 90 | Apache-2.0 |
| HoangNguyen0403/agent-skills-standard | 100 | MIT |
| moustafadev/flutter-ai-skills | 100 | MIT |
| Dee9975/cc-skills-flutter | 100 | MIT |
| Albaylar/Mobile-Development-Kit | 100 | MIT |
| testland/qa | 100 | MIT |
| abdukabirov/flutter-agent-skills | 100 | MIT |
| thiennc-tesoglobal/flutter-skills | 100 | BSD-3-Clause |
| ethiel97/flutter-clean-riverpod-skills | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki d794b36b98c0 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 100bloc-cubit
Pomaga w zarządzaniu stanem we Flutterze z Bloc i Cubit: wybór między nimi, współpraca bloc z flutter_bloc, cykl życia, testowanie i bezpieczne ustawienia domyślne. - 100flutter-bloc-state-management
Wdraża stan, zdarzenia, przejścia i współbieżność asynchroniczną w BLoC i Cubit we Flutterze, w tym zdarzenia z debounce, anulowalne i testy bloc. - 100clean-arch-testing
Pisze i przegląda testy Fluttera w Clean Architecture z Bloc: przypadki użycia, mappery, bloc_test, testy widgetów i testy wizualne. - 100flutter-bloc
Zarządza stanem Flutter przez Bloc i Cubit: zdarzenia, stany, transformery i testy z bloc_test. - 100bloc
Podaje dobre praktyki zarządzania stanem Bloc we Flutter i Dart: Cubit kontra Bloc, nazewnictwo zdarzeń i stanów, klasy sealed z Equatable, podział Page i View oraz BlocBuilder, BlocListener i BlocSelector wraz z testami. - 95testing-flutter
Pomaga pisać testy i strategię testowania aplikacji Flutter 3.47 z BLoC v9 i Riverpod 3.