Skip to content

Instantly share code, notes, and snippets.

@jasonpilz

jasonpilz/unit-testing-javascript.md

Forked from rrgayhart/unit-testing-javascript.md
Last active February 25, 2016 19:16
Show Gist options
  • Save jasonpilz/aad488d1e6c467e25f5d to your computer and use it in GitHub Desktop.
Save jasonpilz/aad488d1e6c467e25f5d 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 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 was surprised by seeing the 'application state' category. This is not something I considered when thinking about components to test.

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

  • I would say I had clear intention of testing the 'data/server communication' category, as well as set up. I feel like the 'presentation & interaction' category would be how I would think of integration tests (I felt this video was referring only to unit tests). The 'application state' category I only considered rarley if ever.

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

@rrgayhart
Copy link

👍

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