Jeff - Appears to be a platform issue with using FileUtils.touch on examples/product.html to force template timestamp update in test/template_file_watcher_test#test_c_file_changed_run. Fix is to cobble in a platform check and force the timestamp change differently on win32. Changed the technique slightly also, believe this is better: a test case really shouldn''t be changing anything in the deliverable files, so the test setup in template_file_watcher_test now makes sure there''s a separate copy of the template file available as its test fixture - copies examples/product.html to test/templates_src/product.html and then uses that copy of the file for testing the file-changed watcher. Do me a favor and rerun that on *nix to reverify, thanks. There''s also a platform issue with test/template_test#test_multi_spec_dir, which tests generation into a specific target output directory(/a/b). On Win32, the mv:generate=''foo/bar'' directive ends up with the current drive letter prefixed to the target path, i.e., ''X:/a/b/foo/bar'' rather than the expected ''/a/b/foo/bar''. I''ll chase that over the w/e to figure out whether it''s a legit issue or if we just need to write the test case a bit differently. ~ Deb