Skip to content

Instantly share code, notes, and snippets.

@acareaga

acareaga/unit-testing-javascript.md

Forked from rrgayhart/unit-testing-javascript.md
Last active February 9, 2016 20:43
Show Gist options
  • Save acareaga/1eba00af5a8494b69580 to your computer and use it in GitHub Desktop.
Save acareaga/1eba00af5a8494b69580 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?)

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 overall divide of the list was most surprising: Presentation & Interaction, Data/Server Communication, Application State, Setup. It makes a lot of sense after hearing Rebecca's talk, especially with being cognizant of what you're actually testing.

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

  • Yes - because of how "new" everything was. I think I also intermingled responsibilities on the list.
@rrgayhart
Copy link

👍

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