Skip to content

Instantly share code, notes, and snippets.

@ShannonPaige

ShannonPaige/testable-js.markdown Secret

Forked from rrgayhart/testable-js.markdown
Last active April 5, 2016 03:31
Show Gist options
  • Save ShannonPaige/f835babe4da3aa99b5fa8b554aef9f72 to your computer and use it in GitHub Desktop.
Save ShannonPaige/f835babe4da3aa99b5fa8b554aef9f72 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?

I think the breakdown makes perfect sense, although I can see myself getting confused about which category certain actions may fall into. For example, interaction vs application state.

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

Yes, mentally, not necessarily in practice though! :) It's a lot of the principals we already use, being ruby developers first. So it aligns very much with how I think about organizing my code.

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