Parsoid/Visual Diffs Testing

The code for generating visual-diffs is in. has code for running a visual-diff server for generating diffs on demand. has code for running testreduce clients, and for configuring the testreduce server.

Visual Diff service
The visual diff service code is in. This service is managed by upstart. The config for this is in   sudo service parsoid_vd stop sudo service parsoid_vd start sudo service parsoid_vd restart (something is broken with the config currently and this doesn't work) Logs are in /var/log/parsoid_vd/parsoid_vd.log. (Hmm .. maybe we should s/parsoid_vd/diffservice/g or something else?)

This visual diffing service is accessible at

Visual-diff testreduce server
The testreduce server instance for doing mass visual-diff testing is in. (In reality, this is just a symbolic link to  and is shared with the testreduce instance used for article roundtrip testing.) The testreduce_vd server settings is in. See that file to access the mysql database used to store testing titles and test results.

Testreduce server logs are in.

Updating the testreduce server code
cd /usr/lib/parsoid-clone git pull sudo service testreduce_vd restart Remember that this code is shared with article roundtrip testing. It should be safe to do this update for both testing services, but just a reminder.

Test results are accessible at http://parsoid-tests.wikimedia.org/visualdiff/

Testing clients
The visualdiff testing clients run on ruthenium. The clients look at the parsoid version deployed in production and rerun tests whenever the deployed version changes.

The clients are managed/restarted by upstart. Config in

To {stop,restart,start} all clients on a VM (not normally needed): sudo service parsoid-vd-client stop sudo service parsoid-vd-client restart sudo service parsoid-vd-client start

Client logs are in.