We already have tests for a few of these -- reconstruct, cyr_info, cyr_deny, cyr_virusscan, quota, and cyr_dbtool tends to get exercised by a lot of tests too -- but it would be good to have basic tests for the various invocations of the rest of the tools. Especially the ones our upgrade documentation refers to!
cyrdump, mbexamine, reconstruct, and a bunch of other tools that I can't recall offhand have been variously broken (and maybe fixed) since the big 3.0 changes, and it would be nice to not have these regress again next time a bunch of major changes go through.
We tend to notice problems with the tools that FastMail use pretty quickly, but there's a lot that we don't use, or only use in one configuration, and problems with the rest go unnoticed till someone else uses them (which is often much later, after a "stable" release).
We already have tests for a few of these -- reconstruct, cyr_info, cyr_deny, cyr_virusscan, quota, and cyr_dbtool tends to get exercised by a lot of tests too -- but it would be good to have basic tests for the various invocations of the rest of the tools. Especially the ones our upgrade documentation refers to!
cyrdump, mbexamine, reconstruct, and a bunch of other tools that I can't recall offhand have been variously broken (and maybe fixed) since the big 3.0 changes, and it would be nice to not have these regress again next time a bunch of major changes go through.
We tend to notice problems with the tools that FastMail use pretty quickly, but there's a lot that we don't use, or only use in one configuration, and problems with the rest go unnoticed till someone else uses them (which is often much later, after a "stable" release).