Unit Testing @ Educ 2016

Unit Testing @ Educ 2016

Talk about unit testing in particular, and automated testing in general, at the 2016 European Dataflex Users' Conference in Berlin

36c905c1a5d3270d1d01a99773256b2d?s=128

Ola Eldøy

May 13, 2016
Tweet

Transcript

  1. 3.
  2. 4.
  3. 5.
  4. 9.
  5. 10.

    UNIT TESTS GIVE YOU A SAFETY NET – INSTANT FEEDBACK

    EXECUTABLE SPECS WORKING SOFTWARE
  6. 15.
  7. 16.
  8. 18.
  9. 20.
  10. 21.
  11. 22.
  12. 23.
  13. 24.
  14. 25.
  15. 26.
  16. 27.
  17. 28.
  18. 29.
  19. 30.
  20. 31.
  21. 36.

    AN INTEGRATION TEST MAY USE THE DATABASE NEEDS A FRESH

    START EVERY TIME STILL NEEDS TO BE AUTOMATED
  22. 37.
  23. 43.
  24. 44.
  25. 48.
  26. 49.
  27. 61.

    NO TIME TO WRITE TESTS? WHAT ABOUT… HAVING CODE THAT

    WORKS THAT YOU CAN CHANGE, REFACTOR
  28. 63.

    IT TAKES A LOT OF TIME "Your tests represent a

    significant investment. They’ll pay off in minimizing defects and by allowing you to keep your production system clean through refactoring. But they also represent a continual cost. You need to continually revisit your tests as your system changes." - Pragmatic Unit Testing in Java 8 with JUnit (Jeff Langr with Andy Hunt & Dave Thomas)