Although we haven't seen it lately, there's a long history of new users tripping over because they haven't used the template to build a local version of this file. I'll be working on the testing.properties issues this weekend, but I wanted to check your view on this similar but unrelated matter...
At the moment, the build loads the contents of the local file with the simple statement:
1. I believe this file is ONLY used by the test target(s), not by any of the run targets.
2. If the file does not exist, or has uninitialised values from the template, I believe the result is that some tests fail because they cannot setup their test data properly. (A long time ago I made one of the tests emit a helpful message, but I forget which).
3. The wiki has a lot of references to this issue when configuring a new sandbox, but it is easy for users to skip over it without realising the eventual consequences.
Unless you can see any drawback, I intend to change the way the build handles this file. I want to create a new target called "prepare-local-accounts" (or prepare-local-test-accounts)
1. The new target will test the availability of the file and fail with a "user friendly" message if it does not exist. (I was not intending to emit a hyperlink to the wiki!)
2. If the file exists, its contents will be loaded without comment. The result of loading an uninitialised template-copy will not change.
3. Obviously, the test target(s) will have a dependency on the new prepare-local-accounts target.
4. Do you think the run target(s) need a dependency on prepare-local-accounts as well?
5. Are there any cruise control issues that I've overlooked?