Re: [FreeWRL-develop] Testing update

[Paulo E. C. <pau...@gm...>]

Hi,

I can confirm that the fixtures generated seem different per machine....
Even when testing in two similar architectures "Linux" the fixtures 
seemed to differ.
I think this might be down to a combination of library versions, graphic 
cards etc ...
Further, I commented the code that was writing the header file of the 
bmp file and that seemed to generate more stable results across runs.
At least I don't have any bit differences between runs.

I used a different approach though ...

First I commented that time reduction hack so that I could record things 
smoothly. 
https://github.com/pecastro/freewrl/commit/4926a80062179dd1223296537eb45bf04b9a17eb

Using recording mode, I manually created one master .fwplay whilst 
moving in the scenegraph back and forth rotating etc and in between each 
move taking some manual snapshots.
This master file was created using the freewrl/tests/2.wrl
https://github.com/pecastro/freewrl/commit/044850835cc7d56e4f6c2b52360485134620e4d3

Then I used this .fwplay file to test all of the .wrl/x3d files.
I iterate over the list of .wrl files to be tested and for each one I 
amend the .fwplay file, and substitute the scenefile for the current 
file being tested.
I then run freewrl in playback mode for that specific .wrl file.
I kept all the headerless .bmp files generated and committed them to a 
local branch.

Then I built freewrl from scratch and ran exactly the same procedure of 
running the script in playback mode and in the end it was a matter of 
asking my source control system if any of those .bmp files had changed.

I never really used the Playback option.

The code hacky has it is can be seen at 
https://github.com/pecastro/freewrl/tree/testing-freewrl

Cheers,



                 PECastro