whatisgithub

What is tests?

flutter/tests — explained in plain English

Analysis updated 2026-05-18

295DartAudience · developerComplexity · 2/5Setup · moderate

In one sentence

A registry of community-contributed test pointers that lets the Flutter team check whether toolkit changes break real, publicly available Flutter apps.

Mindmap

mindmap
  root((flutter/tests))
    What it does
      Registry of community tests
      Checks Flutter changes
    Tech stack
      Dart
      Flutter
    Rules
      Public on GitHub
      No network calls
      Deterministic results
    Use cases
      Register a package's tests
      Catch breaking changes early
    Audience
      Package maintainers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Register your open-source Flutter package's tests so core changes are checked against it.

USE CASE 2

Get notified early if a Flutter toolkit change breaks your public app or package.

USE CASE 3

Look up the rules a test suite must follow to be added to the registry.

USE CASE 4

Understand how the Flutter team verifies changes against real-world usage.

What is it built with?

DartFlutter

How does it compare?

flutter/testsraresense/nova3dgskinnerteam/flutter-sized-context
Stars295146115
LanguageDartDartDart
Last pushed2023-03-23
MaintenanceDormant
Setup difficultymoderatemoderateeasy
Complexity2/53/52/5
Audiencedeveloperdesignerdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 1h+

Contributed tests must run standalone, offline, deterministically, and within about five minutes.

No license information was found in the material provided.

So what is it?

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.

Copy-paste prompts

Prompt 1
Help me write a configuration file to add my Flutter package's tests to this registry.
Prompt 2
Explain the rules my tests must follow to be accepted into flutter/tests.
Prompt 3
How does Flutter use this registry to catch breaking changes before release?
Prompt 4
Show me an example of a valid test pointer configuration for this repo.

Frequently asked questions

What is tests?

A registry of community-contributed test pointers that lets the Flutter team check whether toolkit changes break real, publicly available Flutter apps.

What language is tests written in?

Mainly Dart. The stack also includes Dart, Flutter.

What license does tests use?

No license information was found in the material provided.

How hard is tests to set up?

Setup difficulty is rated moderate, with roughly 1h+ to a first successful run.

Who is tests for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.