Testing @socialstudios.tv

An introduction talk to testing.
Really high level. Some best practices etc.
Python and JavaScript

Transcript

1. Testing @socialstudios.tv Thursday, December 27, 12
2. Debugging Sucks Testing Rocks Thursday, December 27, 12
3. Types of tests unit tests functional tests integration tests behavioral tests UI testing monkey testing stress testing smoke testing usability testing production testing ... Thursday, December 27, 12
4. Today’s Focus: Unit Tests Thursday, December 27, 12
5. The nice thing Testable == Readable == Reusable == Documented == Modular == Robust == Maintainable Thursday, December 27, 12
6. Observation: Tests == Documentation Good tests document the code they are testing If the test passes ⇒ Documentation is up to date They also server as examples Thursday, December 27, 12
7. TDD 1. Write test first 2. Test fails 3. Write code 4. Test passes 5. Commit Red - Green testing Thursday, December 27, 12
8. Good tests are Repeatable Fast Short Test only one thing High coverage Thursday, December 27, 12
9. Bad test are Slow Depend on externals (fb, other websites, db) Require a lot of setup Sometimes pass, sometimes fail Produce a lot of output Have exceptions in the log Thursday, December 27, 12
10. Side Effects are hard to test Good: def f(x): return x * 2 Bad: def g(x): self.y = x * 2 Thursday, December 27, 12
11. Hard to test global variables current time / timing dependent impl untested assumption (such as file load ordering) External state (database) Thursday, December 27, 12
12. External dependencies How do you test facebook? How do you test a DAO (data access object) Thursday, December 27, 12
13. Mocks Use mocks (spies) instead of externals Thursday, December 27, 12
14. UI Testing It’s hard ⇒ only if you must! Use selenium? We have to think about this... Thursday, December 27, 12
15. JavaScript: Jasmine Thursday, December 27, 12
16. Python: unittest2 + nose Thursday, December 27, 12
17. CI Server I’ll work on it... Thursday, December 27, 12
18. test.sh A single file to run them all Thursday, December 27, 12
19. Every Commit must be tested New code: TDD or not it’s your choice. But you have to submit tested code Legacy code: First wrap with tests Then modify Thursday, December 27, 12
20. Resources http://googletesting.blogspot.com http://docs.python.org/2/library/ doctest.html http://pivotal.github.com/jasmine/ http://www.voidspace.org.uk/python/ mock/ Thursday, December 27, 12