logOneFile should use a file with substantial history
Bug #257159 reported by
Martin Pool
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar Usertest |
Confirmed
|
Medium
|
Unassigned |
Bug Description
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://
Changed in bzr-usertest: | |
assignee: | nobody → mbp |
To post a comment you must log in.
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.