Skip to content

Instantly share code, notes, and snippets.

@sekharp

sekharp/unit-testing-javascript.md

Forked from rrgayhart/unit-testing-javascript.md
Last active February 26, 2016 16:49
Show Gist options
  • Save sekharp/06aab5f5ee6237356ad9 to your computer and use it in GitHub Desktop.
Save sekharp/06aab5f5ee6237356ad9 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
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?

  • It's helpful for me to see what Rebecca lists here as best practices. I'm new to JavaScript and hearing what experienced developers see as important rules to follow gives me structure. None of them surprised me per se. It did take me a little while to understand "Application State."

Do you feel like you mentally split your client side code in IdeaBox and other past projects into these responsibilities?

  • I haven't split my code up like this categorization at all though, either on IdeaBox or other past projects. I often have code that deals with many sections at the same time.

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

@rrgayhart
Copy link

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment