Why Your Test Suite Sucks

Why Your Test Suite Sucks

PHP UK Conference via YouTube Direct link

Introduction

1 of 36

1 of 36

Introduction

Class Central Classrooms beta

YouTube videos curated by Class Central.

Classroom Contents

Why Your Test Suite Sucks

Automatically move to the next video in the Classroom when playback concludes

  1. 1 Introduction
  2. 2 Dont do this
  3. 3 Not getting the benefits
  4. 4 Different phases of testing
  5. 5 Where do you learn to test
  6. 6 Why move to automated testing
  7. 7 Issue tracking system
  8. 8 Writing the test first
  9. 9 Design implementation first
  10. 10 Test suites still brittle
  11. 11 Testdriven development
  12. 12 Mock queries
  13. 13 Example
  14. 14 Summary
  15. 15 stubs returning stubs
  16. 16 notifying users
  17. 17 train wreck
  18. 18 user object
  19. 19 double or stub
  20. 20 Validate returns
  21. 21 The problem
  22. 22 Double the validator
  23. 23 Design is important
  24. 24 People worry about writing tests
  25. 25 What happens with TDD
  26. 26 TDD is a way to think about your code
  27. 27 TDD is a complicated one
  28. 28 Testing thirdparty code
  29. 29 Testing objects
  30. 30 Testing framework repository
  31. 31 Testing user repository
  32. 32 Double repository
  33. 33 Example of double repository
  34. 34 Cloud API
  35. 35 Interface
  36. 36 Dont Test

Never Stop Learning.

Get personalized course recommendations, track subjects and courses with reminders, and more.

Someone learning on their laptop while sitting on the floor.