Christian Johansen is a Norwegian developer who writes about Clojure, Emacs, Go, JavaScript testing with Sinon.JS, and Rails deployment.
HN links it for Clojure and Emacs tutorials, including a deps.edn guide that a commenter calls wonderful, and older Rails and Git server guides.
Use JsTestDriver to write and run your tests.
One of my pet projects is open source and tested with JsTestDriver [1], that should be a good starting point for learning more about how to test JavaScript in webapps.
I also like to use Sinon [2] for stubbing and mocking. The author of Sinon is also putting the finishing touches on a book about TDD-ing JavaScript.
EDIT: calendar-logic.js [4] an example of how you can extract and test logic in separate libraries. It's being used on figureoutwhen.com.
[1] http://github.com/augustl/figureoutwhen.com
[2] http://cjohansen.no/sinon/
[3] http://www.amazon.com/Test-Driven-JavaScript-Development-Developers-Library/dp/0321683919
[4] http://ditrw.com/calendar-logic-dot-js/
It's not really intended as an "evangelist" post. It's just describing some details that makes a big difference to me in my day-to-day work. I guess it's more of a "hey, fellow Clojure programmer, don't you agree that these details really put the icing on the cake?" kind of post.
Maybe the other post I posted the same day would give newcomers a better impression of what using Clojure is like in practice (lots more code, more in-depth): http://cjohansen.no/building-static-sites-in-clojure-with-stasis
I found the original linked page much more descriptive than the Ajaxian summary: http://www.cjohansen.no/en/ruby/juicer_a_css_and_javascript_packaging_tool Juicer is written in Ruby. You need Java too if you want to use JsLint and YUI Compressor.
Read the Ajaxian comments before you use. One personal rightfully noted that you shouldn't add parameters for cache-busting because it'll also bust server-side proxies/caches. The right way to do this is to rename the file, which Juicer supports.
You could run something like Autotest for continuous testing & quality control: http://ph7spot.com/musings/getting-started-with-autotest
You can run Capistrano for continuous deployment: https://github.com/capistrano/capistrano.
If you wanted to go the extra mile you could also setup different staging environments on your server:
http://cjohansen.no/en/rails/multi_staging_environment_for_rails_using_capistrano_and_mod_rails
What I really like about deps.edn is the ability to add git repos and also local projects as deps. Makes forking and testing libraries a charm.
Another wonderful tutorial about using deps.edn that contains additional tips for Emacs -- https://cjohansen.no/tools-deps-figwheel-main-devcards-emacs/
If you need a git server for your company, why not set up Gitorious?
The initial setup can be quite challenging, but I found this guide to be quite useful: http://cjohansen.no/en/ruby/setting_up_gitorious_on_your_own_server