logOneFile should use a file with substantial history

[Martin Pool]

At the moment usertest runs 'bzr.1.5 log zzzDir/zzzFile', and that is created by a previous add/commit command.

If we're running on a branch that has substantial history it would be nice to test a file which itself has a long history itself.

One possibility would be to automatically pick a file from the tree that's likely to meet this criteria (and that will of course be stable across runs.) Another option is to use the parameterization facility to set it per-tree
<http://people.ubuntu.com/~ianc/plugins/usertest/doc/usertest-tutorial.html#providing-parameters-to-scripts> but this may mean people don't get the most useful output by default.

[Martin Pool (mbp)]

So it seems like we need to pick a file name based on what's present in the directory, and then substitute that into the log command. For many trees a name like Makefile* is likely to be both present and sufficiently frequently modified to be interesting. However, the precise name will vary per tree.

We could make this a configuration option, or we could teach it to choose a file from the tree.

[Martin Pool (mbp)]

http://people.ubuntu.com/~ianc/plugins/usertest/doc/usertest-tutorial.html#providing-parameters-to-scripts

It would be nice if the scripts still work if this is not provided.

[Martin Pool (mbp)]

A drawback of using a configuration setting is that it makes the test less easily reproducible: people have to have not just the same test data but also set the same configuration.

[Martin Pool (mbp)]

Not working on this any more, and I didn't get very far.