Hi, On Tue 29/05/12,12:54, Michael Whapples wrote: > As for extending the JSON test files for other cases, I have some ideas. It > mainly revolves around an idea that a "type" field could be given > to specify what type of test is to be performed (if type is not given then > the standard translate test is assumed), and then one gives > relevant fields for that test type, some fields may be required others might > be optional. This should mean that all test types would be > fairly compact. Agree, Attila and I are already working on this, although personally I will not have much time before the weekend. new fields so far: 'comment': a n optional comment field to describe the purpose of the test. 'direction': [f/b] forward/backward translation, if omitted assumes forward. The more tricky one is how to do we want to represent mask information, compactly, for tests for bold/italic etc. > I still see advantages to the doctest system as it provides examples and can > run any type of code, however it seems harder to support python2 > and python3 in a single file for them. If we need more flexibility, that the standard harness doesnt give, the test writer can always write test_xxx which can test any functionality that may be required. They are fully valid python functions. This should also be still more cross compatible with p2/p3 than the doctests. How do you feel about this? Mesar For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com