That's always been my gripe with client-side JS tests as well. For large frameworks or libraries (like jQuery), I'd definitely unit test in a heartbeat, but for

That's always been my gripe with client-side JS tests as well. For large frameworks or libraries (like jQuery), I'd definitely unit test in a heartbeat, but for end-developer code which is mostly code fired after the DOM is ready, calling plugins verbatim, and binding user input to actions, Selenium is really a much better use of my testing time than adding in unit tests for those particular use cases.