- From: Roland Gülle <roland@7val.com>
- Date: Thu, 17 May 2007 20:42:06 +0200
- To: Sean Owen <srowen@google.com>
- Cc: public-mobileok-checker@w3.org
Hi Sean, >> I think we have crossed wires here. I was thinking of test cases >> for the >> pre-processor to process, I think, e.g. broken HTML etc. (which it >> trips >> up on at the moment) I'm guessing that some of these at least need >> to be >> in php or whatever to generate the appropriate HTTP header errors. >> >> This is probably worth discussing in more depth. > > Oh that's already in place, see for example: > http://dev.w3.org/cvsweb/2007/mobileok-ref/test/data/ROOT/ > CachingTest/1/ > > You place a doc as well as a file full of the headers that should be > sent back with it, along with expected test results. The test > framework does the rest: runs Tomcat, serves the docs with the > headers, and compares results against the given results document. This sounds cool to test the complete process and check if all components work together. But for testing the components separate, especially the XSLTs, we should also create input (moki) - output (???) documents for the transformations. I don't have much experience with Tomcat and Java, so writing/testing at the command line is much easier for me (and maybe for others too). If this is only 'my' problem, I'll spend some time for setup a tomcat on my linux box... Roland
Received on Thursday, 17 May 2007 18:42:28 UTC