Advanced JavaScript Unit Testing
Last week analytics team has participated in “Israel JavaScript Conference” organized by E4D.
One of the interesting lectures was the one talking about how (and why) we should test our UI code.
Three tools were presented: Qunit, which provides in-browser testing, JSTestDriver, to perform headless tests (tests without a GUI), and Sinon.JS, a tool for stubbing & mocking JS.
All those tools are fully integrated with visual studio, and meant to be used as a part of a CI (Continuous Integration) process. For example, we in analytics use Team City as a build server. One of the tools above, JS Test Driver, can be integrated into Team City, see how.
Written by Yehuda Zargarov
Related protips
Have a fresh tip? Share with Coderwall community!
JavaScript on a page runs with the privileges of that origin. One altered library, tag manager, or snippet can read inputs, change what people see, and call your APIs as the user.
Security insights from Cside