should support testing particular bzr formats
Bug #277398 reported by
Martin Pool
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar Usertest |
Confirmed
|
Medium
|
Unassigned |
Bug Description
It would be useful to specify to usertest that a particular tool configuration should use a bzr format.
At the moment there is a hardcoded special case:
80 self.compile_
81 cd ..
82 $tool init --development ${work_
83 cd ${work_
84 $tool pull ../$work_basename
85 """)
86
It would be better if the format could be configured and, if it's not the default, either an upgrade or init and pull would be run before testing starts.
Changed in bzr-usertest: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
To post a comment you must log in.
At present scripts can use compile_ for_versions, which must match against the name of the tool. That seems appropriate if it really is something that depends on the tool version, like a particular command being present or not. But setting the data format is not really dependent on the tool version, more a matter of how we want to test it.