0
Integration tests? No, thanks.
A A A  B B T A B   T AB   T B
A A A  B B T A B   T AB   T B
A A A  B B T A B   T AB   T B
A A A   B B T A B   T AB   T B
A A A   B B T AB   T AB   T B
A A A   B B T AB   T AB   T B
A A A   B B T AB   T AB   T B
A A A   B B T AB   T AB   T B
A A A   B B T A B   T AB   T B
A A A   B B T A B   T AB   T B
A A A   B B T A B   T AB   T B
integration  tests  are  integrated   tests
integrated   tests are  agglomerate  tests
Are your tests  agglomerate ?
agglomerate  tests  are   slow
agglomerate  tests  have big setup
agglomerate  tests  have too many assertions
agglomerate  tests  not focused
agglomerate tests  give poor feedback
agglomerate  tests  cover 20% of values
business values follow  ABC rule
80% value  =  20% items
agglomerate  tests  have poor coverage
agglomerate  tests  are too many
agglomerate  tests  are combinatory explosive
agglomerate  tests  loss business values
avoid  agglomerate tests
with  collaboration   tests
over  contract   tests
collaboration  over  contract
basic correctnes
focused object tests
trust platform
don't test libraries
good object tests
collaborator tests
contract tests
contract tests
you will   reduce tests
you will   en rich feedback
you will   effective coverage
?
Luca Marrocco [email_address] twitter.com/lucamarrocco Luca S Lopomo [email_address] twitter.com/neuromancer977
Upcoming SlideShare
Loading in...5
×

integration test? no, thanks

799

Published on

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.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
799
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
6
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Transcript of "integration test? no, thanks"

  1. 1. Integration tests? No, thanks.
  2. 2. A A A B B T A B T AB T B
  3. 3. A A A B B T A B T AB T B
  4. 4. A A A B B T A B T AB T B
  5. 5. A A A B B T A B T AB T B
  6. 6. A A A B B T AB T AB T B
  7. 7. A A A B B T AB T AB T B
  8. 8. A A A B B T AB T AB T B
  9. 9. A A A B B T AB T AB T B
  10. 10. A A A B B T A B T AB T B
  11. 11. A A A B B T A B T AB T B
  12. 12. A A A B B T A B T AB T B
  13. 13. integration tests are integrated tests
  14. 14. integrated tests are agglomerate tests
  15. 15. Are your tests agglomerate ?
  16. 16. agglomerate tests are slow
  17. 17. agglomerate tests have big setup
  18. 18. agglomerate tests have too many assertions
  19. 19. agglomerate tests not focused
  20. 20. agglomerate tests give poor feedback
  21. 21. agglomerate tests cover 20% of values
  22. 22. business values follow ABC rule
  23. 23. 80% value = 20% items
  24. 24. agglomerate tests have poor coverage
  25. 25. agglomerate tests are too many
  26. 26. agglomerate tests are combinatory explosive
  27. 27. agglomerate tests loss business values
  28. 28. avoid agglomerate tests
  29. 29. with collaboration tests
  30. 30. over contract tests
  31. 31. collaboration over contract
  32. 32. basic correctnes
  33. 33. focused object tests
  34. 34. trust platform
  35. 35. don't test libraries
  36. 36. good object tests
  37. 37. collaborator tests
  38. 38. contract tests
  39. 39. contract tests
  40. 40. you will reduce tests
  41. 41. you will en rich feedback
  42. 42. you will effective coverage
  43. 43. ?
  44. 44. Luca Marrocco [email_address] twitter.com/lucamarrocco Luca S Lopomo [email_address] twitter.com/neuromancer977
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×