Thanks, Mesar. This looks good. John On Wed, Feb 22, 2012 at 03:46:45PM +0000, Mesar Hameed wrote: > Hi Christian, > > On Wed 22/02/12,10:15, Christian Egli wrote: > > > I feel that many problems can be found and ironed out if the liblouis > > > had an extensive test harness for the various tables. > > > > I'd be happy to work with you on this. > > Thanks, this would be great. > > > > This is how I personally managed to quickly find a somewhat working > > > solution. > > > > Are you saying you have some kind of test harness? > > Yes, attached, not sure if it is as flexible as we want it to be, but it did > the job for me. > > 1. Create a harness directory at the same level as tables, tools etc. > 2. Place the two attached files there. > 3. cd harness; python runHarness.py > > All the test data is stored in the *_harness.py file. > each table that should be tested should have its own harness file with test > cases. > Each file specifies the table, and the test cases that should be run against > it. > Each test should have: > A comment explaining the purpose of the test. > (unicode) text input, > (ascii braille) expected braille output. > > The expected output for test 3 is deliberately wrong to show you the format > for when a test fails. > > The harness file is simple and should hopefully encourage people to > contribute tests for their tables. > > If you have suggestions for improving or extending this please let me know > and I will see what can be done. > > Thanks. > Mesar -- John J. Boyer; President, Chief Software Developer Abilitiessoft, Inc. http://www.abilitiessoft.com Madison, Wisconsin USA Developing software for people with disabilities For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com