User blog comment:TOR/Caching Explained/@comment-3335785-20130327230944/@comment-4674838-20130328035540

When developing JS or CSS, it's best to do your live tests in-browser. There is no need to publish an edit just to test JS or CSS. For JavaScript, use your browser console in the developer tools. For CSS, use Firebug or other browser extensions (here's a simple one for Chrome) which will satisfy your CSS testing needs.

Doing all your primary testing in-browser is not only faster than publishing an edit &mdash; it also guarantees that you're seeing your most recent version of code take effect, rather than it being stuck on a cached version. As part of your testing, I would also highly recommend running JS through JSHint or CSS through a CSS validator before deploying your code.