FakeCommand allows the test author to make sure that a command is invoked with a particular workingDirectory, environment, and/or encoding. However, the expect calls have their parameters swapped.

For example, a test including this snippet:

processManager.addCommand(
  const FakeCommand(
    command: <String>[sdkManagerPath, '--licenses'],
    exitCode: 1,
    environment: <String, String>{
      'JAVA_HOME': 'expected value'
    },
    stderr: 'crash',
  ),
);

Can result in output looking like this:

00:01 +0 -1: uses JDK bundled with Android Studio when validating license acceptance [E]                      
  Expected: {}
    Actual: {'JAVA_HOME': 'expected value'}
     Which: has different length and has extra map key 'JAVA_HOME'

Relevant code: