Stop wasting time NOT writing tests

Stop wasting time NOT writing tests

It's a common mistake that tests take lots of time, while actually the truth is that initial manual testing is the overhead. Kickout manual testing and never ask time for writing tests - make them a part of your workflow.

5f81e2d2889d7642fd84c8b24db7ee17?s=128

DamirSvrtan

October 03, 2015
Tweet

Transcript

  1. Stop wasting time NOT writing tests

  2. How many of you are developers?

  3. How many of you test your applications?

  4. Some just do manual testing…

  5. Characteristics of manual testing

  6. 1. Repetitive

  7. 2. Slow

  8. 3. Error prone due to human memory capacity

  9. “Whatever can be automated will inevitably be automated” - Bob

    Lord, president of AOL
  10. What is automated testing?

  11. Automated testing is a process of writing and executing scripts

    which will simulate a user using our application before it get’s released to production.
  12. How is it better than manual testing?

  13. Slow Repetitive Error prone due to human memory capacity

  14. Why people don’t write tests? #excuses

  15. “The application is too small to write tests for it.”

  16. Small applications tend to grow.

  17. “writing tests is boring”

  18. Is clicking around your application whenever something changes, fun?

  19. “we don’t have a specification, tests are no use at

    all.”
  20. STOP. Arrange a meeting with your project manager and sort

    s**t out.
  21. “We don’t have time to write tests”

  22. None
  23. It doesn’t take extra time to write tests

  24. The wrong way: manually test write code write tests

  25. Never separate the application and tests

  26. The right way: write code write tests

  27. You’re not wasting time on automated tests - you’re wasting

    time on initial manual testing
  28. Testing API’s

  29. None
  30. Don’t check your implementation in the browser - from the

    beginning do it through tests.
  31. Testing large forms

  32. None
  33. Shouldn’t QA engineers handle the testing phase?

  34. Simple bugs hide the more advanced ones

  35. Let QA engineers focus on improving the UX, security, weird

    edge cases…
  36. BAD GOOD GOOD EXCELLENT

  37. Test Driven Development

  38. order number Order Container identification number Product order date details

    product name Shipment tracking application Ship name
  39. My order XYZ shipped on December 21st containing 3 cases

    of beers, travelling with ship named MARSHALL inside a container with an ID 161
  40. My order XYZ shipped on December 21st containing 3 cases

    of beers, travelling with ship named MARSHALL inside a container with an ID 161
  41. IF I ENTER: XYZ

  42. December 21st

  43. beer

  44. MARSHALL

  45. 161

  46. I SHOULD FIND MY ORDER

  47. KNOW THE OUTPUTS FOR GIVEN INPUTS

  48. Improve your specification through tests.

  49. How to start writing tests?

  50. Writing tests is hard..

  51. Is programming hard?

  52. Writing tests is a discipline of it’s own..

  53. ..but as hard as learning a set of design patterns.

  54. Developer: I want to start writing tests

  55. Product manager / client: we don’t have time for that,

    we should work on our new features
  56. TRY A DIFFERENT APPROACH

  57. Make tests part of your development cycle

  58. Conclusions

  59. Kick out manual testing!

  60. Don’t ask for time to do tests - just do

    them!
  61. Damir Svrtan Rails Team Lead @ Infinum Organizer @ Ruby

    Zagreb Meetup Hit me up on twitter @DamirSvrtan