Register your open-source Flutter package's tests so core changes are checked against it.
Get notified early if a Flutter toolkit change breaks your public app or package.
Look up the rules a test suite must follow to be added to the registry.
Understand how the Flutter team verifies changes against real-world usage.
| flutter/tests | raresense/nova3d | gskinnerteam/flutter-sized-context | |
|---|---|---|---|
| Stars | 295 | 146 | 115 |
| Language | Dart | Dart | Dart |
| Last pushed | — | — | 2023-03-23 |
| Maintenance | — | — | Dormant |
| Setup difficulty | moderate | moderate | easy |
| Complexity | 2/5 | 3/5 | 2/5 |
| Audience | developer | designer | developer |
Figures from each repo's GitHub metadata at analysis time.
Contributed tests must run standalone, offline, deterministically, and within about five minutes.
This repository is a registry of tests contributed by people outside the Flutter team. Flutter is a toolkit for building apps that run on phones, tablets, and the web. When the Flutter team makes changes to the toolkit, they need to know whether those changes accidentally break real apps that developers are already building. This registry is how they do that. The repository does not contain the actual app code being tested. Instead, it holds small configuration files, each pointing to a separate public GitHub repository where someone's real project or test suite lives. When Flutter runs its automated checks, it reads these pointers and runs the referenced tests to confirm nothing is broken. Anyone can add their project to the registry by following a set of rules. The tests must be publicly available on GitHub, must not reach out to the internet or depend on external services, must always produce the same result each time they run, must produce no output when they pass, and must finish within roughly five minutes. The goal is a reliable signal: if your tests are in the registry and a Flutter change makes them fail, the Flutter team finds out before that change is released. This is a tool for the Flutter development process itself, not something a typical app developer would interact with directly. It is most useful to developers who maintain open-source Flutter packages or apps and want to ensure the Flutter team is aware of how core changes affect their work.
A registry of community-contributed test pointers that lets the Flutter team check whether toolkit changes break real, publicly available Flutter apps.
Mainly Dart. The stack also includes Dart, Flutter.
No license information was found in the material provided.
Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.