Test Context Arrangement Recipebook
14 likes2,531 views
The document discusses strategies for testing Rails applications. It recommends: 1. Writing model unit tests first to cover the core functionality. 2. Using different data strategies like fixtures, fixture replacements, and before blocks depending on the type of data (e.g. master, resource, event data). 3. Sharing testing contexts with descriptive names to clearly express intentions and reduce fatigue when adding new tests. The key ideas are to choose suitable data strategies for different data types and use naming conventions to make tests more maintainable.
Test Context Arrangement Recipebook
- 1. 5 years know-how of RSpec driven Rails app. development MOROHASHI Kyosuke (@moro)
- 2. Kyosuke MOROHASHI ✓ http://twitter.com/moro ✓ http://github.com/moro ✓ Eiwa System Management, Inc.
- 5. aigi byK rice Ru l p cia off spe % 40 http://tatsu-zine.com/books/cuke
- 6. able o vail -D A Ju nku igi @ yKa Rub http://amzn.to/rails3recipebook
- 8. 5 years know-how of RSpec driven Rails app. development MOROHASHI Kyosuke (@moro)
- 10. I’ll talk about. ✓What test should I write first? ✓ Write model unit test. ✓I began model test,but it’s difficult to setup data!! ✓ Use multi strategies for multi types of data. ✓It seems good but less DRY. Is there any idea? ✓ Share your testing context.
- 11. m le ob Pr What test should I write first?
- 12. on ti lu So Write Model unit test.
- 13. People say Skinny Controllers Fat Models
- 14. It’s clear what happening. http://flic.kr/p/5tk4by
- 15. #64 2011-07-18 12:00 http://twitter.com/railstokyo
- 16. aigi byK rice Ru l p cia off spe % 40 Use Cucumber (or other end-to-end testing) to cover controller, views and more. http://tatsu-zine.com/books/cuke
- 17. Model unit test
- 18. m le ob Pr Began model test, but it’s difficult to setup data!!
- 19. events students courses lessons registrations rooms periods
- 20. Course-1 Course-2 Period-1 Lesson-1-1 Lesson-2-1 Period-2 Lesson-1-2 Lesson-2-2 Period-3 Lesson-1-3 Lesson-2-3 Period-4 Lesson-1-4 Lesson-2-4 Period-5 Lesson-1-5 Lesson-2-5 registration
- 21. Course-1 Course-2 Period-1 Lesson-1-1 Lesson-2-1 Period-2 Lesson-1-2 Lesson-2-2 Period-3 Lesson-1-3 Lesson-2-3 Period-4 Lesson-1-4 Lesson-2-4 Period-5 Lesson-1-5 Lesson-2-5 registration
- 22. Course-1 Course-2 Period-1 Lesson-1-1 Lesson-2-1 Period-2 Lesson-1-2 Lesson-2-2 Period-3 Lesson-1-3 Lesson-2-3 Period-4 Lesson-1-4 Lesson-2-4 Period-5 Lesson-1-5 Lesson-2-5 registration
- 26. on ti lu Use multi So strategies for multi types of data.
- 27. ✓ 3 types of data ✓ 3 strategies
- 28. ✓ 3 types of data ✓ 3 strategies
- 29. ✓ Master data ✓ Resource data ✓ Event data
- 30. Mastar data ✓ Created/updated rarely. ✓e.g. rooms / periods. ✓ Less dependencies to others. ✓ Maintained by or so.
- 31. Resource data ✓ Mainly created/updated data. ✓ Users themselves maintains this type of data.
- 32. Event data ✓ Represent relationship between resources. ✓ Used for ‘s through table in Rails.
- 33. ✓ 3 types of data ✓ 3 strategies
- 34. ✓ Fixture ✓ Fixture replacement ✓ block
- 36. ✓ good speed to be loaded. ✓ less maintainability. ✓ less flexibility.
- 38. ✓ flexible. ✓ powerful but difficult to use correctly. ✓ slow to be loaded.
- 40. Which should we use rails-fixture or fixture replacement? Use them both which suitable for the data.
- 41. block
- 42. ✓ each run per test. ✓ same speed with real data persistence. ✓ edit each of them to maintain.
- 43. flexibility maintain- speed in test ability good for Master fixture best wrong wrong data fixture Resource wrong good best replacements data good for each Event before() good best wrong for all data
- 44. events students Resource courses lessons registrations Event rooms periods Master
- 46. on ti lu Use multi So strategies for multi types of data.
- 48. ✓ fixture ✓ fixture replacement ✓ block Use them all which suitable for the data.
- 49. m le It seems good ob Pr but less DRY. Is there any idea?
- 50. Students Course Count Period-1 Lesson-1-1 2 Period-2 Lesson-1-2 3 Period-3 Lesson-1-3 3 Period-4 Lesson-1-4 3 Period-5 Lesson-1-5 2
- 54. on ti lu So Share your testing context.
- 56. ✓ naming each ✓ naming them
- 57. ✓ naming each ✓ naming them
- 58. “ Generates a method whose return value is memoized after the first call.
- 59. ✓ name each focusing object. ✓ Build strategy doesn’t matter.
- 60. ✓ naming each ✓ naming them
- 61. ✓ RSpec’s ✓ ✓
- 63. A student subscribes a course event lesson-1-1 lesson-1-1 course-1 lesson-1-1 lesson-1-1 lesson-1-1 registrations registrations registrations registrations Alice <student> room-1 room-1 period-1 period-1 room-1 room-1 period-1 period-1 room-1 period-1 course-2 lesson-2-1 lesson-2-1 lesson-2-1 lesson-2-1 lesson-2-1
- 66. ✓ naming each w/ ✓ naming them w/ Express your intention clearly and reduce tiredness to add new test.
- 67. on ti lu So Share your testing context.
- 68. Conclusion
- 69. I’ve talked about. ✓What test should I write first? ✓ Write model unit test. ✓I began model test,but it’s difficult to setup data!! ✓ Use multi strategies for multi types of data. ✓It seems good but less DRY. Is there any idea? ✓ Share your testing context.
- 70. ✓ fixture ✓ fixture replacement ✓ block Use them all which suitable for the data.
- 71. ✓ naming each w/ ✓ naming them w/ Express your intention clearly and reduce tiredness to add new test.
- 72. May a test be with you.
- 75. May a test be with you.