The document discusses different testing philosophies for software, including unit testing, functional testing, integration testing, and acceptance testing. It also discusses philosophies of test-driven development, testing everything, unit independence, integration testing only, and a combination of unit and integration testing. The document provides definitions and examples of different testing approaches and encourages discussion on testing strategies.

1. Testing Philosophies by Rob Kaufman Notch8 notch8.com [email_address]

2. What are Testing Philosophies

4. Functional Test – Does a whole set of methods accomplish what they set out too

5. Integration Test – Do the software components work together as desired

6. Acceptance Test – Does the user see/get what they expect

7. The When

8. The What

10. You can’t test code that isn’t there

11. Tests are just as likely to contain bugs

12. Should focus on code reviews, writing good code and user level testing (acceptance tests)

14. Considered a great developer

15. Hates automated code testing

17. Is really a whole school of philosophies

18. Often is thought to include some sort of CI tool, but doesn't have to

20. Should test the interface (input and output) of a method and any side effects

21. Test should focus on a given part of an individual method

22. Tests should only rely on themselves and nothing else (1)

23. In classic rspec model, controller and view tests are all focused at unit levels

25. Use mocks and stubs

27. Similar to acceptance testing, but automated and programmatic

28. Cucumber, Fitness, etc are common tools for this

30. Do functional testing at the controller level

31. Do integration testing at the view level

32. Is the default in Rails with Test::Unit

34. Merb Request specs

35. Request specs will become the default rSpec test for Rails 3

36. Throw Down?

37. Discussion!