Presentation about best development practices for JavaScript teams.

1. Productive JavaScript workflow
Krzysztof Szafranek

2. Happy beginnings

3. Happy beginnings

4. 11 years later...

5. 2 years
> 80 000 lines of JavaScript
4 major redesigns
15 front-end developers

6. Do you test every change in each browser?
Before each commit?
× ×

7. Are you sure you didn’t break
any page in the application?

8. Do you know if you didn’t
break somebody else’s code?

9. You don’t know

10. How to stay sane while
working on a large JS project?
Krzysztof Szafranek

11. Part I
e basics

13. jslint will hurt your feelings
Early

15. Unit testing

16. “But we don’t have time to
write tests!”
“My manager didn’t want unit
tests”

17. How do you know your code
works, when you don’t have a
test for it?

18. How do you know your code
still works aer each commit,
when you don’t have a test for
it?

19. You don’t know

20. Added bonus:
Refactorings are a breeze

21. Refactoring
without tests

22. Which framework?
DOH Jasmine RhinoUnit
JSUnit screw-unit JasUnit
QUnit Test.Simple FireUnit
Crosscheck Test.More Js-test-driver
J3Unit TestCase Sinon.js
JSNUnit TestIt SOAtest
YUITest jsUnitTest Vows
JSSpec JSTest Nodeunit
UnitTesting JSTest.NET Tyrtle
JSpec jsUnity

23. Doesn’t matter
(As long as you use it)
(And is easy to automate)

24. JS Test Driver

25. How about testing layouts?

26. Part II
Putting it all together

27. Running tests in every
browser takes time
People make mistakes

28. Automation to the rescue!

29. Continuous Integration is a soware development practice
where members of a team integrate their work frequently . . .
leading to multiple integrations per day. Each integration is
verified by an automated build (including test) to detect
integration errors as quickly as possible.
Martin Fowler

30. CI for front-end
push
jslint deploy
tests

32. Early bug detection
Early fixes
No more FTP uploads
Application is always shippable

33. Warning!

34. Part III
Humans are useful, too

35. Pair programming

36. Best debugging tool ever

37. Code reviews

38. .. soware testing alone has limited effectiveness – the average
defect detection rate is only 25 percent for unit testing, 35
percent for function testing, and 45 percent for integration
testing. In contrast, the average effectiveness of design and
code inspections are 55 and 60 percent.
Steve McConnell
Code Complete

40. A little help from the process
Not Checked Code Design QA
Started Out Review Review Review
Are
there
unit
tests?

41. Before we part
1. Use jslint and unit tests to get feedback early
2. Use CI to have shippable soware all the time
3. Don’t be afraid of your peers (and ducks)

42. Links
http://www.jslint.com/
http://code.google.com/p/js-test-driver/
http://jenkins-ci.org/
http://sinonjs.org/

43. krzysztof@szafranek.net
Photo credits:
SpoiltCat, RemixDave, activeside, kate.gardiner, Jiheffe