![Testing Antipatterns ,[object Object],[object Object]](https://image.slidesharecdn.com/opensourcebridgetestingantipatternspresentation-120116222024-phpapp02/85/Open-source-bridge-testing-antipatterns-presentation-1-320.jpg)
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Similar a Open source bridge testing antipatterns presentation
Similar a Open source bridge testing antipatterns presentation (20)
Último
Último (20)
Open source bridge testing antipatterns presentation
- 2. Anti - What?
- 5. Who has an extensive test suite?
- 6. Who feels like they should test more?
- 7. Who dislikes, even dreads, writing tests?
- 8. Testing Can Be Fun Text Text Text Text http://xkcd.com/583/
- 9. For example:
- 10. Red Green TDD Addiction
- 11. Testing Framework Games (although these can be a distraction) (although these can be a distraction)
- 12. Not looking like an idiot - that’s fun right?
- 15. Antipatterns that have bitten me the most
- 16. Not Running Tests Often Enough
- 17. If it’s Hard and Important Do it More Often
- 18. testing, deploying, releasing, exercising, meditating, writing, public speaking
- 20. Not Fixing Broken Tests Before Committing New Code
- 21. The Slowpoke
- 22. How Slow Is Too Slow?
- 23. Unit Test Suite Took 8 Hours to Run - On One Project
- 24. Single Test Took 2 Minutes to Start
- 25. So slow that rewriting it in PHP would make it faster
- 27. The Mockery
- 28. Why mock when the real things will do?
- 29. Testing at the Wrong Level
- 30. unit, smoke, functional, integration, acceptance
- 31. Success Against All Odds (test never fails) (test never fails)
- 33. Testing Implementation Instead of Behavior
- 35. Testing Behavior
- 37. You’ve got too much global state
- 38. Excessive Setup
- 39. What are we testing again?
- 41. Summary
- 42. Avoid Antipatterns and Testing Can Be Fun
Notas del editor
- Ask questions whenever you want
- Talk about Design Patterns general reusable solution to a commonly occurring problem
- Realized while writing this talk that I was focusing on what pissed me off and made me not want to talk about it. Should be humor in testing.
- Red failing Green passing
- Not really an antipattern since it’s really only solving being lazy
- CI essentially glorified cron job
- The Joel Test #5: Fix bugs before writing new code Mention Lava Lamps
- Martin Fowler Mocks aren't Stubs. Never met a mockist whose tests I liked. Not mocking means mini integration tests. Possibly controversial. When to mock: code you don't control - file system, web server, external libraries like ssl
- Too much mocking might indicate this
- Everyone has their own terms
- Test Driven Development prevents this
- Behaviour Driven Development is a larger term with more meaning
- These are annoying but can’t be ignored. How to find these failures - binary search.
- Testing antipatterns can indicate antipatterns in your implementation code
- Data driven web apps tend to be even worse