FLUTTER_REPO_DIR ==> FLUTTER_ROOT?

FLUTTER_ROOT is already taken

But shouldn't it point to the same place? I should have said, what about using FLUTTER_ROOT below instead of defining a new var?

Because this alias is defined in .bashrc or .profile this variable will be globally visible, and therefore you won't be able to have both a checkout of the repo and a normal installation of Flutter (e.g. from the alpha branch). If we use FLUTTER_ROOT it will cause all Flutter installations to point to the same location, which might result in surprising behavior.

FLUTTER_REPO_DIR would only point to a working checkout of Flutter, and it would not affect other installations of it.

I'm fine with switching over to FLUTTER_ROOT if the alternative behavior is what we actually want.

It looks like this example is just illustrative of how someone might set up a script to test their checkout; I didn't intend to bikeshed on it too much :) Happy w/ how you have it now.

I wouldn't bother talking about this. People should just use test.sh and if they know that they can look in that file to figure out how to do individual subparts of it.

Gone.