Test that flutter run doesn't introduce new debug spew #111577
Description
I think I'm right in saying that #110948 was able to emerge undetected in stable because we don't have a test that verifies flutter run does not spew out an unexpected error.
Can we add such a test? Here is the failing condition:
[C:\src\wintext] flutter run -d windows
Launching lib\main.dart on Windows in debug mode...
Building Windows application...
[ERROR:flutter/shell/platform/windows/direct_manipulation.cc(137)] CoCreateInstance(CLSID_DirectManipulationManager, nullptr, CLSCTX_INPROC_SERVER, IID_IDirectManipulationManager, &manager_) failed
[INFO:embedder.cc(136)] populate_existing_damage was not defined, disabling partial repaint. If you wish to enable partial repaint, please define this callback.
Syncing files to device Windows... 58ms
We should have been able to pick this up with CI by identifying unexpected text between the Build command and the Sync command. I suspect a test like this might pick up a whole category of potential failures that might only otherwise be detected with manual testing.
/cc @loic-sharma for thoughts.