- 1: Finish up VisualTest.
- 2: Convert one of the playpen tests over.
- 3: Get a sample plugin containing that test building and running in the Sample Browser.
Hmmm, alright then. tuan kuranes had suggested this sort of thing early on and I'd assumed it would be helpful, but I suppose HTML output alone would be sufficient. I could see such a comparison tool being helpful by allowing for some advanced comparison modes (using shaders to highlight differences could be interesting), but I do suspect it would be a lot of work for not a whole lot of actual practical use.Assaf Raman wrote:Why do we need such a tool? This feel to me really off topic.
We talked about an HTML output - why do we need a complicated tool? In what the tool better then the HTML output?
What need for OGRE is the option to run a sort of batch process, I was planning to take your work and have a process where every night it is run, and uploaded to a web site - giving the community a day by day status of the project.
The tool can be nice, but not much then that. The focus should be giving a summary output of the sate of the project. This is what we need.
I'm not especially familiar with build server stuff, but given the specs I could definitely make it generate output that's usable there.Wolfmanfx wrote:Take into account an xml or file output so that the results can be evaluated from build server. If you stick with an standard xml output (like cppunit) most build server can parse these xml files.