Expand deprecation policy to package:flutter_test

[Piinks]

This is the tracking issue for the proposal to expand the deprecation policy to package:flutter_test

When first introduced, we decided to first focus the application of the deprecation policy on just the flutter package. During that time we worked on the process and gathered feedback from users. This process has become pretty stable, and so we are looking to expand it to other packages, with the first being flutter_test.

This will involve:

• adding dart fix support to flutter_test
  • Add dart fix capabilities to flutter_test #123154
• advance communication to users and a feedback period
  • https://groups.google.com/g/flutter-announce/c/nwVUWwsX_mM
• deprecation notice formatting enforcement
• updating the deprecation policy on the wiki and website to list enforced packages

If we were to do this after the next release (not the current round that completed with #119580 but the next round), these would be up for removal:

class / method	property	deprecated in
AnimationSheetBuilder	display	2.3
AnimationSheetBuilder	sheetSize	2.3
TestWidgetsFlutterBinding	addTime	2.6
TestWidgetsFlutterBinding	runAsync	2.6
TestWidgetsFlutterBinding.runTest	timeout	2.6
AutomatedTestWidgetsFlutterBinding.runTest	timeout	2.6
LiveTestWidgetsFlutterBinding.runTest	timeout	2.6
testWidgets	initialTimeout	2.6

cc @goderbauer @pdblasi-google

[gslender]

Is this appropriate place to raise issues with depreciation of methods and classes (in the flutter_test package) that are still needed because no equivalent method or class exists?

[Piinks]

Is this appropriate place to raise issues with depreciation of methods and classes that are still needed because no equivalent method or class exists?

Definitely! I think all of the listed APIs have migration paths, but if we are missing one we certainly would love to know!

[workerbee22]

If we are extending to flutter_test would you consider also integration_test (now also part of the framework)? Then all core testing components covered 🤔 Because lets face it, Dart fixes for flutter_test would largely also appy to Dart code used within integration_test?

[Piinks]

If we are extending to flutter_test would you consider also integration_test (now also part of the framework)?

Great question! The long term goal is to expand the policy to cover all packages in flutter/flutter, and maybe even dart:ui. 🙂

We're just doing this at a considerate pace since it means more potential breaking changes for developers.

[pdblasi-google]

@Piinks I added a link to a ticket for adding dart fix support to the description. I plan on starting on it in the next couple weeks, hopefully early next week.