Skip to content

Instantly share code, notes, and snippets.

@toriejw

toriejw/unit-testing-javascript.md

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

    None of the responsibilities surprised me, though I wasn't thinking of client side code in this way before.

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

    I split each feature up similarly to this (starting with the presentation, and then moving to server communication via setup), but I did not think of the entire application in this way.

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