Hi Shane, I like the idea of using a file-naming convention to separate different processor's output. I was thinking of a slight variation to your proposal. What if we arbitrarily picked the output of one of the processors and gave it just the extension .out, and then any processor's which differed in output would append their processor "identifier" to the output name. For example,
output1.out output1-xalanjC.out output2.out output2-xalanc.out output3.out In this example, the output from XalanJ (interpreted) corresponds to the .out files. The output from xalanjC (XSLTC) differed for output1. The output from xalanc (Xalan-C++) differed for output2. All processors produced the same output for output3. For some reason, I find this less confusing. Also, although I wouldn't expect this to happen often, what if output changed from version to version of a particular processor? In this case you would want to change the corresponding .out file, but you wouldn't to cause failures if you ran the test buckets against earlier versions of the processor. Could cvs tagging play a role here? Thanks, Ilene. -------------- Shane wrote: +1 to storing just the gold files that need to be different separately; BUT, I'd propose an alternate to the directory trees: -- Have accept-gold/ as a single tree, but use a file-naming convention to separate out different processor's output. This would make defaulting to a base gold that all processors can use easier anyways. Like: accept-gold/output/ outputDiff01-xalanc.out outputDiff01-xalanjI.out outputDiff01-xalanjC.out outputSomeSame01.out outputSomeSame01-xalanc.out Here, all processors have different outputs for outputDiff, but xalanjI and xalanjC have the same effective output for outputSomeSame - however xalanc does have a difference here. A filenaming scheme like this makes it easier to see the similarities/differences; simpler on a large scale to maintain since the same kind of output files are right next to each other; and would be fairly easy to implement a defaulting scheme in the output file name construction (if this processor-specific name isn't available, go for a name that's generic).
