flutter_test has src imports on packages test_api and matcher

This is unsound in general, and makes it impossible to unpin these packages as part of #158050

Examples:

flutter/packages/flutter_test/lib/src/test_compat.dart

Line 14 in 9d96df2

    
           import 'package:test_api/src/backend/declarer.dart'; // ignore: implementation_imports

flutter/packages/flutter_test/lib/src/matchers.dart

Line 18 in d81cd3e

    
           import 'package:matcher/src/expect/async_matcher.dart'; // ignore: implementation_imports

One possibility is to expose all the depended upon code in the public api.

@sigurdm

@sigurdm Thanks for the detailed report. As the issue is related to flutter_test, which is a first-party package in the Flutter repo, labeling this under team-ecosystem for further triage.

I believe flutter_test is team-framework, but please redirect if I'm mistaken.

Taking a look!

It looks like to resolve this

package:matcher will need to :
- Expose AsyncMatcher in the public API (e.g., in package:matcher/expect.dart or package:matcher/matcher.dart).
package:test_api will need to:
- Expose the following backend classes in package:test_api/backend.dart:
  - Declarer
  - Group
  - GroupEntry
  - Invoker
  - LiveTest
  - Message
  - State
  - Test

The matcher and test_api packages are owned by the dart team, is exposing these classes something that can be done?

@jakemac53

/cc @jakemac53 and @natebosch who had weighed in on the comment thread about this in the unpinning doc.

Technically it's something that can be done, and if flutter is anyways using them there isn't much of a philosophical difference.

We could expose these only through test_api and not test_core or test, which would alleviate some of the concerns around breakage (breaking versions of test_api are less concerning).

Probably the largest question mark would be around AsyncMatcher in matcher.

Sent out dart-lang/test#2635 - but no promises it will land :D

Expose the backend APIs used by flutter_test from test_api (#2635)

This issue is marked P1 but has had no recent status updates.

The P1 label indicates high-priority issues that are at the top of the work list. This is the highest priority level a bug can have if it isn't affecting a top-tier customer or breaking the build. Bugs marked P1 are generally actively being worked on unless the assignee is dealing with a P0 bug (or another P1 bug). Issues at this level should be resolved in a matter of months and should have monthly updates on GitHub.

Please consider where this bug really falls in our current priorities, and label it or assign it accordingly. This allows people to have a clearer picture of what work is actually planned. Thanks!

I can work on a PR for the test_api bits

Looks like there are many packages that will end up having to be upgraded, and using the update packages tool did not actually update test_api and friends, so I am not sure how to proceed here.

There is some issue due to test/analyzer/archive interactions, archive is pinned and causing some issues. I will see if I can work my way out of this mess but I am going to timebox it.

Note that either some were missed or some have been added, but there are additional types now that will need to be exposed by test_api as well. But we can get rid of some of the src imports still, and I can send an additional PR to expose the missing ones.

So I realized that this will also have to be coordinated with google3... and yeah I don't think I can take that on.

I will send a PR to test_api for the additional APIs to expose.

export additional types from package:test_api/backend.dart (#2745)

Navigation Menu

Repository navigation

flutter_test has src imports on packages test_api and matcher #185016

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

flutter_test has src imports on packages test_api and matcher #185016

Description

Activity

saurabh-mirajkar commented on Apr 14, 2026

stuartmorgan-g commented on Apr 14, 2026

Piinks commented on Apr 14, 2026

Piinks commented on Apr 14, 2026

stuartmorgan-g commented on Apr 15, 2026

jakemac53 commented on Apr 27, 2026

jakemac53 commented on Apr 27, 2026

jakemac53 commented on Apr 27, 2026

flutter-triage-bot commented on Sep 1, 2026

jakemac53 commented on Sep 2, 2026

jakemac53 commented on Sep 2, 2026

jakemac53 commented on Sep 2, 2026

jakemac53 commented on Sep 2, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions