Skip to content

Instantly share code, notes, and snippets.

@danjwinter

danjwinter/testable-js.markdown Secret

Forked from rrgayhart/testable-js.markdown
Last active April 4, 2016 13:32
Show Gist options
  • Save danjwinter/eb0e4469943b1278230b47ab36ad5edc to your computer and use it in GitHub Desktop.
Save danjwinter/eb0e4469943b1278230b47ab36ad5edc to your computer and use it in GitHub Desktop.
Download ZIP
Writing Testable JavaScript
Raw
testable-js.markdown

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 particularly surprised me but it was nice to see her break them out in such a manner because I've been lacking a proper framework to split up my logic.
  • Do you feel like you mentally split your client side code in IdeaBox and other past projects into these responsibilities?
    • My idea box code is broken up a little bit but by and large it is exactly what she is rallying against. And I completely agree that breaking up your code into testable pieces is paramount to quality.

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

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