[DO NOT SUBMIT] format test

[goderbauer]

Diff produced on CI:

diff --git a/lib/web_ui/dev/build.dart b/lib/web_ui/dev/build.dart
index df1fe19123..0000000000 100644
--- a/lib/web_ui/dev/build.dart
+++ b/lib/web_ui/dev/build.dart
@@ -28,34 +28,29 @@ class BuildCommand extends Command<bool> with ArgUtils<bool> {
argParser.addFlag(
'watch',
abbr: 'w',
-      help:
-          'Run the build in watch mode so it rebuilds whenever a change is '
+      help: 'Run the build in watch mode so it rebuilds whenever a change is '
'made. Disabled by default.',
);
argParser.addFlag(
'host',
-      help:
-          'Build the host build instead of the wasm build, which is '
+      help: 'Build the host build instead of the wasm build, which is '
'currently needed for `flutter run --local-engine` to work.',
);
argParser.addFlag(
'profile',
-      help:
-          'Build in profile mode instead of release mode. In this mode, the '
+      help: 'Build in profile mode instead of release mode. In this mode, the '
'output will be located at "out/wasm_profile".\nThis only applies to '
'the wasm build. The host build is always built in release mode.',
);
argParser.addFlag(
'debug',
-      help:
-          'Build in debug mode instead of release mode. In this mode, the '
+      help: 'Build in debug mode instead of release mode. In this mode, the '
'output will be located at "out/wasm_debug".\nThis only applies to '
'the wasm build. The host build is always built in release mode.',
);
argParser.addFlag(
'dwarf',
-      help:
-          'Embed DWARF debugging info into the output wasm modules. This is '
+      help: 'Embed DWARF debugging info into the output wasm modules. This is '
'only valid in debug mode.',
);
}
@@ -170,3 +165,4 @@ class NinjaPipelineStep extends ProcessStep {
return startProcess('autoninja', <String>['-C', buildDirectory, ...targets]);
}
}

[flutter-dashboard]

It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!).

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group.