A complete introduction to unit testing, and test-first development for AngularJS programmers. Topics include tools, specs, test runners, core testing practices and patterns, Behavior-driven development, Spys, Matchers, Stubs and MOcks and much more.

1. describe('UnitTes.ng',
func.on(){
it('works
with
AngularJS'…
}
Jesse
Liberty
Master
Consultant
Falafel
SoFware
jesse@falafel.com
@jesseliberty

2. What We Will Cover
• Why
bother?
• Why
Aren't
We
Doing
It?
• Wri.ng
specs
• Matchers
• Spies

3. Getting the terms right
§ Unit Test
§ Test Driven Development (TDD)
o Test First Development
§ Behavior Driven Development (BDD)

4. Am I In The Right Presenta7on?
• I
assume…
• Comfort
with
Angular
Fundamentals
• No
prior
experience
with
unit
tes.ng

5. Ques7ons
If
you
get
lost
it
will
be
hard
to
catch
up
so
please,
please
ask
ques.ons
Copyright
©
2003-­‐2014
Falafel
SoFware
Inc.
5
Q&A
at
the
end

14. Getting Started
§ What you already need to know
o Javascript
o Angular
§ What hardware you need
§ What software you need
§ Where to get everything
o Getting Jasmine
o Finding documentation
o Finding Help

15. jasmine.github.io

17. Red, Green, Rafactor
§ Red – Your Test Should Fail
§ Green – Make Your Test Pass
§ Refactor – Clean up your code without breaking your test

18. Red, Green, Rafactor
§ Red – Your Test Should Fail
§ Green – Make Your Test Work
§ Refactor – Clean up your code without breaking your test
Lather
Rinse
Repeat

19. Three Laws
1. You may not write production code until
you have a failing test
2. You may not write more of a unit test than
is sufficient to fail
3. You may not write more production code
than is sufficient to pass

20. The Prime Directive
§ Your test code should be as good and well maintained as your
production code.
o Succinct
o Clear
o Simple
§ However, do not worry about efficiency in test code

21. Test One Concept In Each Test
§ Pass/Fail should immediately convey what was tested and the result

22. F.I.R.S.T.
§ Fast
§ Independent
§ Repeatable
§ Self-validating (boolean output)
§ Timely

23. SEE:
Setup
Execute
Check Expectations

24. Wri7ng Your First Spec

34. Demo

35. Measuring your step size

39. Matchers

40. Matchers
§ toBe
§ toEqual
§ toBeTruthy
§ toBeNull, toBeUndefined, toBeNaN
§ toContain
§ toMatch
§ toBeLessThan
§ etc.

54. Demo

62. Demo

63. Custom Matchers
• How
would
we
test
that
an
expense
item
is
"reasonable?"
• Problem
#1
–
We'd
like
to
use
"ToBeReasonable"
• Problem
#2
–
How
will
the
compare
pick
out
the
amount
as
the
value
to
test?
new
ExpenseItem(
'taxi',
'Taxi
to
airport',
89.50);

64. Custom Matchers

69. Demo

71. Making An Expense Item
§ Delete expense.js
§ Add new parameters to ExpenseItem

74. Requirement:
Persist
expenses
and
report
number
that
were
persisted

81. Demo

83. Ques7ons?
Contact
me:
jesse@falafel.com
@jesseliberty

84. Contact Me
• Jesse
Liberty
• Falafel
SoFware
• jesse@falafel.com
• @jesseliberty