{"thread":{"id":"13712","subject":"gitweb: Smoke test","startedAt":"2008-05-28T18:56:33Z","lastAt":"2008-05-28T18:56:33Z","messageCount":1,"participants":["Lea Wiemann"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"77971","messageId":"483DAAE1.4000107@gmail.com","threadId":"13712","inReplyTo":null,"subject":"gitweb: Smoke test","fromName":"Lea Wiemann","fromEmail":"lewiemann@gmail.com","sentAt":"2008-05-28T18:56:33Z","receivedAt":"2008-05-28T18:56:33Z","isPatch":false,"sender":{"key":"lewiemann@gmail.com","avatar":null},"body":"FYI and in case you're interested, I've implemented a smoke test for \ngitweb in a branch, here: \nhttp://repo.or.cz/w/git/gitweb-caching.git?a=tree;f=gitweb/test;h=cccee14b2571200861ffc05fbfae12c6d17e919d;hb=HEAD\n\nIt spiders your local gitweb site (which preferably only contains a \nreally small test repository) with wget, and reports any problems, i.e. \nbroken links or crashes of the CGI script.\n\nThe same mechanism might also be usable to view recursive diffs between \nold and new output, to see if anything has changed.  I'll probably \nimplement that later when I start doing refactorings on gitweb.  Perhaps \nwe should also have a real test suite at some point, though I'm not \nentirely sure yet how to approach that -- I'll have to dig into the code \nfirst. :)\n\n(If there's any desire to copy the script to mainline, let me know -- \nI'll be happy with leaving it on the branch for now, though.)\n\n-- Lea\n"}]}