Skip to content

Instantly share code, notes, and snippets.

@jwperry

jwperry/testable-js.markdown Secret

Forked from rrgayhart/testable-js.markdown
Last active April 6, 2016 02:37
Show Gist options
  • Save jwperry/0151fbca234d7d42a955032de8c59b85 to your computer and use it in GitHub Desktop.
Save jwperry/0151fbca234d7d42a955032de8c59b85 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 wouldn't say I'm terribly surprised by any of the responsibilities she lists, but I suppose setup would be the most confusing one. I actually really started to get a deeper understanding of the separation between client and server side code while working on GameTime, so I feel as though the others (presentation & interaction, data/server communication, and application state) all make a lot more sense to me now than they would have previously.

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

    • No. In IdeaBox, everything was so new with JavaScript that this wasn't even on my radar, and I definitely didn't have a solid understanding of the differentiation between client/server side. I feel as though I could do a lot better with this now.

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