John McCabe-Dansted <[email protected]> writes: > I don't think we have discussed what the benefit of having keystest > in-tree is. LyX can run without keytest, and keytest can be applied to > software other than LyX, so it is not strongly coupled to LyX, and > splitting it off would be a possibility. I am thinking of using > keytest as a general tool to test any software that has a rich > keyboard accessible GUI, at which point it may make sense to split it > off from LyX. Keytest is at 150K, and AFAICT I am the only person who > uses it. At what point does the overhead of keeping keytest in the LyX > tree outweigh the benefit?
If you make it usable for programs other than LyX, then I think it would make a lot of sense to split it off. 150k is no overhead for LyX, but having something in LyX which is a copy of a program distributed separately is an overhead. >> Uhhm.. I'm not sure whether I'll like that all the output is added to >> svn too. What do others think? > > As of yet keytest has found ~50 bugs. Each of the recipes is about 100 > bytes. So the recipes for all known automatically generated bugs would > take 5k, compared to 150k for all of keytest. I don't have a strong > belief that this information really belongs in svn, but it is small > compared to the rest of keytest. I think it is not a matter of size. It is better to have all bug reports into the bug tracker, instead of adding a new place where to look. JMarc
