Guys, I've been using the XSLTCized comparator by setting the following property in my "test.properties" file:
conf.xsltc.fileChecker=org.apache.qetest.xsl.XHTFileCheckServiceXSLTC Tom Santiago Pericas-Geertsen wrote: > > On Tuesday 03 December 2002 14:50, Shane Curcuru wrote: > > The XSLTC folks tweaked this particular output comparison routine a > > while back, but I can't seem to find references to it in active code in > > CVS. Are we still using this today, or not? > > I thought so, but I couldn't find any references either. I remember we were > using a property for this, but I can't find it in the build.xml file. > > > If we are, then (since we're talking about improving other conformance > > test comparisons anyway) can we fold the basic differences back into > > XHTFileCheckService? > > Yes, I'd be great to use the same comparator for both processors. > > > (And each underlying XHTComparator, which is the > > important difference). I thought the only major change was in > > diff(...) to test getLocalName/getNamespaceURI separately (in the > > *XSLTC one) rather than just testing getNodeName as-is. > > Yes, that was one of the diffs. The other had to do with the location of > namespace declarations --I believe XSLTC's comparator was simply ignoring NS > declaration, which helps reduce the noise at the expense of an occasional > false pass. Another diff was the use of JTidy to compare HTML output, but as > I said, I'm not sure that this is being used in the current CVS. > > -- Santiago -- Tom Amiro -- SQE Engineer WTS - Interoperability and Quality voice: 781-442-0589 Fax: 781-442-1437 eMail: [email protected]
