Skip to content

Instantly share code, notes, and snippets.

@marlomajor

marlomajor/unit-testing-javascript.md

Forked from rrgayhart/unit-testing-javascript.md
Last active April 15, 2016 15:53
Show Gist options
  • Save marlomajor/d277ce2618c3a6e1973d to your computer and use it in GitHub Desktop.
Save marlomajor/d277ce2618c3a6e1973d 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?
  • Presentation/Interaction, and Setup are obvious to me, but data server communication and application state are things I normally just don't think about. Those were definitely surprising to me. Now...to incorporate this aha moment into my code...
  • Do you feel like you mentally split your client side code in IdeaBox and other past projects into these responsibilities?
  • Only after building the entire application in one module was I able to extract the responsibilities and split the code into their respective responsibilities. For me, this was an easier way to understand the beginning of JavaScript.

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

@marlomajor
Copy link
Author

@rrgayhart

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