[integration_test] Throw a graceful error when attempting to run `flutter drive --web-renderer skwasm`

[Rexios80]

Use case

This command pretends to work, but the launched web build is broken: flutter drive --web-renderer skwasm

The proper command is as follows: flutter drive --wasm

This has caused me confusion in the past due to the command structure of running dart tests compiled to wasm: dart run -p chrome -c dart2wasm

See https://github.com/flutter/flutter/issues/150947

Proposal

Throw a graceful error like flutter run --web-renderer skwasm instead of launching a broken web build

[Rexios80]

I found where this error is supposed to be thrown: https://github.com/flutter/flutter/blob/b9b0784ea4089ee394c0ba92658bd4d25e466b9d/packages/flutter_tools/lib/src/commands/run.dart#L671

But it appears validateCommand isn't getting called for flutter drive somehow

[huycozy]

Thanks for the proposal. For context, when running the test with flutter drive --web-renderer skwasm, there is an error on browser's console that makes the Flutter program hang (the detail use case is on https://github.com/flutter/flutter/issues/150947):

Uncaught (in promise) FlutterLoader could not find a build compatible with configuration and environment.

[andrewkolos]

I found where this error is supposed to be thrown:

https://github.com/flutter/flutter/blob/b9b0784ea4089ee394c0ba92658bd4d25e466b9d/packages/flutter_tools/lib/src/commands/run.dart#L671

But it appears validateCommand isn't getting called for flutter drive somehow

The code pointed out here is for the run command. Perhaps it should be moved from RunCommand to the parent RunCommandBase, which DriveCommand also extends.

[Rexios80]

You are totally right! For some reason I thought that code was in the base class.