|
From: doug s. <hig...@ho...> - 2013-04-22 18:52:09
|
> > > ... When I do testing there are 50 or so .wrl/.x3d test > > > files I run. > > > http://dug9.users.sourceforge.net/web3d/tests/screenlinks.html > > > Plus depending on what I'm tinkering with, I'll set up special > > > .wrl/.x3d test files, and I've accumulated some samples people have > > > sent in. > > > > > Can you describe your testing process a bit better ? Do you mean you > > manually open the files and play with them to assert the validity of > > the code ? > > Manually open the file, manually click/drag the mouse, visually look at > the scene and compare with my memory of what the scene looked like > before fhe change. > One developer Michel attempted more automated testing via commandline > string containing mouse input (haven't tried it, not sure if it still > works or how advanced it was, would have been at least a few years > ago). > Recently we were wondering if it's possible/how to do more automated > testing with graphical programs. We have a way to 'dump' a scene (as > text, showing scenegraph) to a file. And we have a way to do a screen > snapshot (to an image file). One more idea: have some way to specify > the number of loops to advance (perhaps also time?) But nothing > working today as automated test suite. Paulo, There was also an idea of a record mode in freewrl: specifically: - number of frames - input: keystroke, mouse action - snapshot - dumpscene And perhaps put it in a special file format, for playback during testing. To make the number of frames smaller -so the tests run faster- the record mode could purposely run slow - pausing on each frame. -Doug |