Am 23.06.2011 um 23.Jun - 12:25 schrieb Stuart Yeates:
> My thoughts were along the lines how we add even more functionality to the transformations without introducing subtle errors. The software engineer in me though that "unit testing" might be the answer, so I've been casting around without success for something suitable. I ended up writing a blog post about what I see the requirements are in the hope that someone else has already shaved this particular yak:
> For these without a technical background, unit testing is a software engineering approach whose goal (to quote the wikipedia page) "is to isolate each part of the program and show that the individual parts are correct." It is currently all the rage in technical circles, for apparently good reason.
At present I am working on a back transformation from HTML5 to TEI. When the stylesheet is sufficiently complete, and the obvious forth and back transformation errors have been removed it should be relatively easy to write an automated test. After a forth and back transformation the original should have been regained ignoring insignificant white space etc.
Then one can set up a large number of small TEI XML's and HTML5's on which this is runs.
All the best, Eberhard
Dr. Eberhard von Kitzing
E-Mail: [log in to unmask]
Tel.: 06221 385129 (Wochenende)
Tel.: 02405 419788 (H)
Tel.: 02405 413524
Mob: 0172 2419568