integration test? no, thanks
If you can't read please download the document
DESCRIPTION
integration test appear to be interesting to verify a system. there are many problem related to this test. we try to present the problem (that is essentially related to a design problem) that force to use a group of test that give poor feedback. we offer two simple solutions to improve this kind of tests: collaboration and contract tests.TRANSCRIPT
- 1. Integration tests? No, thanks.
2. A A AB B T A B T AB T B 3. A A AB B T A B T AB T B 4. A A AB B T A B T AB T B 5. A A A B B T A B T AB T B 6. A A A B B T AB T AB T B 7. A A A B B T AB T AB T B 8. A A A B B T AB T AB T B 9. A A A B B T AB T AB T B 10. A A A B B T A B T AB T B 11. A A A B B T A B T AB T B 12. A A A B B T A B T AB T B 13. integrationtestsareintegrated tests 14. integrated tests areagglomeratetests 15. Are your testsagglomerate ? 16. agglomeratetestsare slow 17. agglomeratetestshave big setup 18. agglomeratetestshave too many assertions 19. agglomeratetestsnot focused 20. agglomerate testsgive poor feedback 21. agglomeratetestscover 20% of values 22. business values followABC rule 23. 80% value=20% items 24. agglomeratetestshave poor coverage 25. agglomeratetestsare too many 26. agglomeratetestsare combinatory explosive 27. agglomeratetestsloss business values 28. avoidagglomerate tests 29. withcollaboration tests 30. overcontract tests 31. collaborationovercontract 32. basic correctnes 33. focused object tests 34. trust platform 35. don't test libraries 36. good object tests 37. collaborator tests 38. contract tests 39. contract tests 40. you will reduce tests 41. you will en rich feedback 42. you will effective coverage 43. ? 44. Luca Marrocco [email_address] twitter.com/lucamarrocco Luca S Lopomo [email_address] twitter.com/neuromancer977