From: Tony G. <Ton...@Su...> - 2004-01-30 14:29:20
|
There's nothing quite like moving scripts from one machine to another to really show the scripts' dependencies on an idiosyncratic directory structure. I did that: I copied the previous xmlroff-testing package to a different machine, and nothing worked. So I fixed it. If there'd been a bug reported about it, I expect I would have fixed it sooner. Can someone try it out to see if it works for them so I can close bug 886125? The testing setup still needs work so it's easier to test the different xmlroff backends and output types: for example, right now the scripts, etc. are hardwired for PDF files, with no option of generating or manipulating PostScript files. I will be filing some RFEs just to get the necessary changes on the record. If anyone else wants to help, working on the testing setup would be a good way to help xmlroff without having to delve into the xmlroff source code: all that's needed is a bit of XSLT and Perl knowledge. I said before that I wanted to to monthly releases. This month's release is the xmlroff testing setup. I did mean xmlroff itself, so I don't know if releasing the testing setup obeys the letter but not the spirit or the spirit but not the letter of what I said before, but that's what's released this month. From the news item about it: ------------- The xmlroff test setup automatically runs xmlroff on the XML and FO files in one or more testsuites. It also compares a test's output against its reference and produces a summary report indicating which tests produce differing output. Lastly, the record of the test results can be updated from the HTML page showing the test results. This release removes a lot of the idiosyncratic file system dependencies of the 0.2.0 release, makes it easier to create an initial testresults.xml file, and groups the common parameters into a testing-param.xsl file. --------------- Regards, Tony Graham. |