Cucumber is not for testing

As a pure testing tool, Cucumber falls short. From this point of view, there is a lot wrong with it. But is it really a test framework?

Transcript

1. Cucumber is not for testing Wednesday, 12 June 13
2. Documentation? Wednesday, 12 June 13
3. System design? Wednesday, 12 June 13
4. Communication Wednesday, 12 June 13
5. Communication between stakeholders, product managers and devs Wednesday, 12 June 13
6. Wednesday, 12 June 13
7. There are better ways of testing rspec + capybara Wednesday, 12 June 13
8. Wednesday, 12 June 13
9. End to end is Expensive Wednesday, 12 June 13
10. How do we get the best out of Cucumber? Wednesday, 12 June 13
11. Declarative steps Wednesday, 12 June 13
12. Wednesday, 12 June 13
13. Wednesday, 12 June 13
14. Why is this better? Wednesday, 12 June 13
15. Why is this better? The ‘how’ is unstable Wednesday, 12 June 13
16. Why is this better? The ‘how’ is unstable Boring Wednesday, 12 June 13
17. Why is this better? The ‘how’ is unstable Boring Better errors Wednesday, 12 June 13
18. Modules Wednesday, 12 June 13
19. Don’t nest steps Wednesday, 12 June 13
20. Wednesday, 12 June 13
21. Define methods, just not in your step definitions Wednesday, 12 June 13
22. Wednesday, 12 June 13
23. Wednesday, 12 June 13
24. Wednesday, 12 June 13
25. Restrict scope Wednesday, 12 June 13
26. Model parts of your world and push behaviour onto them Wednesday, 12 June 13
27. Wednesday, 12 June 13
28. Wednesday, 12 June 13
29. Wednesday, 12 June 13
30. Talk, not test Wednesday, 12 June 13