chore: add flutter/tests customer testing script#1528
Conversation
|
In my opinion the supabase_flutter packages does not contain enough tests to make this really worth it. The majority is not even really related to Flutter itself but rather Dart only tests. |
Since it's very little work for us to have this (no maintenance cost) in the test registry, I think this is good to have set up for the future when there will be more test. A full suite of integration tests with all features are planned for example. |
Adds a registry entry for [supabase-flutter](https://github.com/supabase/supabase-flutter), the official Supabase client library for Flutter/Dart, so that framework changes are checked against its tests as a presubmit. Follows the same pattern as the Flame entry (#489): the entry clones supabase-flutter at a pinned commit and runs `scripts/customer_testing.dart`, which: 1. Runs `flutter analyze --no-fatal-infos` over the whole pub workspace (covers every member package). 2. Runs `flutter test` in `packages/supabase_flutter`. Only `supabase_flutter` is exercised because it is hermetic (mock/stub based). The repo's other packages have tests that require a live Supabase backend, so they are not included here. The `scripts/customer_testing.dart` script is added in supabase/supabase-flutter#1528. contact: [email protected]
3 participants
What
Adds
scripts/customer_testing.dart, the entry point invoked by the flutter/tests registry to run this repository's tests as a presubmit againstflutter/flutterframework changes.This is the supabase-flutter counterpart of what Flame did in flutter/tests#489. A companion PR to
flutter/testsadds theregistry/supabase_flutter.testentry that clones this repo at a pinned commit and runs this script.What the script does
flutter analyze --no-fatal-infosover the whole pub workspace (covers every member package).flutter testinpackages/supabase_flutter.Only
supabase_flutteris exercised because it is hermetic (mock/stub based). The other packages' tests require a live Supabase backend and are therefore not eligible for the registry, which requires hermetic tests (no network, no spawned services).Why
So that Flutter framework regressions affecting
supabase_flutterare caught upstream, before they reach a stable Flutter release.Notes
dart run scripts/customer_testing.dartpasses (analyze clean, 57 tests pass).Part of SDK-1216