Testing

JanusWeb is a complicated project with a lot of moving parts, it would be a good idea to set up an automated testing system to verify changes before they're pushed live.

Unit testing

Elation, Elation Engine, and Cyclone Physics Engine have some basic tests, but their coverage is low and we don't have a standardized test runner. JanusClientConnection is self-contained and should be easily unit testable. JanusWeb itself could have unit tests for functionality like room parsing, room edits, etc, or that functionality could be moved into the JanusClientConnection library.

Acceptance testing

Probably the easiest way to do acceptance testing would be to keep a list of URLs which show off a wide variety of Janus functionality, and use Selenium to load each URL, take a screenshot, and automatically compare it to a screenshot of the same URL in previous versions. If the images differ by more than a certain threshold, the developer should be able to see both images side by side to determine whether the change is an improvement or a regression.

URL list

The following URLs are good tests of various functionality:

Room Name	URL	Features
Lobby	http://www.janusvr.com/lobby.html	Portals, lightmaps, particles, sounds, websurfaces, transparency, dae, obj
Playroom	http://q.vrsites.com/playroom/	default primitives with tex0 and color override, images, websurfaces
Reddit - /r/vrsites	https://www.reddit.com/r/vrsites	Reddit translator, dae, portals with thumbs, lightmaps, websurfaces
The Penguin that Escaped the Zoo	http://amy.vrsites.com/4/424/	Layered images with transparency, animated gifs
Adventure Story	http://goo.gl/iFo2Mc	sounds, text, obj, textures
Q-ster's Office	http://goo.gl/RP4raZ	obj, negative scale, cull_faces, images, sbs3d, shaders, websurface
XXX VR Sites	http://xxxvrsites.com/	videos (2d, sbs3d), mirror portal, websurface
Dot Matrix	http://usagii.net/index.php?p=dotmatrix	Nearest texture filter, transparency, gifs
404 Page	http://asdf.com/akjdhihriurh	HTTP error translator, OBJ, animated gifs