unit-testing-javascript.md

Step One: Watch Writing Testable JavaScript - Rebecca Murphey from Full Frontal 2012 (award for worst conference name ever?)

Step Two: Fork this gist.

Step Three: Consider the four responsibilities that Rebecca lists for client side code (hint: they're color coded).

• Did any of the responsibilities that she lists surprise you?
• Do you feel like you mentally split your client side code in IdeaBox and other past projects into these responsibilities?

Step Four: Totally Optional: take a look at some of the other forks and comment if the spirit moves you.

• Other than the fact that the presenter burped and it was watery, this was a good video. Firstly, she made me realize why testing is so invaluable for future-proofing. I always considered testing just something that I need to get a 4, but thinking about a codebase 5 years down the road, I probably won't want people banging down my door to fix my old code.
• At first I was like, "WUT?," but the principles made since once she explained them. I think setup was the weirdest one for me because I never really thought about testing it/separating it out/etc. I am still trying to move away from the whole "OMG IT WORKS" and trying to go back and refactor, test individualized pieces better, and make sure everything is in its right home.
• NO I DID NOT! My Ideabox was one big cluster.....thing and I am very surprised Steve didn't smack my computer off my desk. I had everything in one large document ready and just blasted through functions with reckless abandon. Whoo go Jill!

I just lol'd at that first line

👍