Testing Spree Stores and Extensions - M. Scott Ford

Transcript

1. Testing Spree Stores and Extensions M. Scott Ford Software Engineer Cardagin Networks
2. About me
4. 0:23
6. If my code failed people could die
7. Structure of the talk Four parts: 1. Why test? 2. Testing best practices 3. Testing Spree stores 4. Testing Spree extensions
8. Why Test?
9. Why is Testing Important?
10. Safety Critical vs. Mission Critical
11. Safety Critical If my code fails, people could die.
12. Safety Critical Aircraft and Spacecraft
13. Safety Critical Emergency Response Systems
14. Safety Critical Passenger Rail
15. Mission Critical If my code fails, business is impacted.
16. Mission Critical Mars Science Lab Landing
17. Mission Critical Stock Trading Software
18. Mission Critical E-Commerce
19. Why Don't We Test More Often?
20. Why don't we test more often? "Testing is frustrating."
21. Why don't we test more often? "I don't see the benefit"
22. Why don't we test more often? "I don't have time"
23. Why Test? Summary Why is Testing Important? Safety critical vs. Mission critical Why Don't We Test More Often?
24. Best Practices
25. Test First vs. Test Last
26. Different Levels of Testing These are the kinds of tests that this talk is going to cover Acceptance Integration Unit
27. Other Kinds of Tests These tests are important, but we don’t have enough time to go into them here. Security Performance Exploratory
28. Properties of a Good Test Reads like a story (beginning, middle, and end) Easy to read and understand what’s being tested
29. Tool Choice Cucumber vs. RSpec vs. Test::Unit vs. others
30. Tips for Consultants Don’t list testing as on giant line item in your estimate Don’t make testing optional Let your client's risk tolerance dictate how much you test
31. Best Practices Summary Test first vs. test last Properties of a good test Different levels of testing Tool choice Tips for consultants
32. Testing Spree Stores http://github/mscottford/sample-store
33. Getting Started Create a new spree store project with RSpec and Capybara http://github.com/mscottford/sample-store branch: master
34. Create a Rails App $ gem install rails -v 3.2.8 $ rails _3.2.8_ new sample-store --skip-test- unit
35. Add Spree $ echo "gem 'spree', '~> 1.1.0'" >> Gemfile $ bundle update $ rails g spree:install $ echo "/public/spree" >> .gitignore
36. Add RSpec and Capybara Gemfile: group :test do gem 'rspec-rails' gem 'capybara' gem 'database_cleaner' gem 'factory_girl' gem 'faker' end
37. Add RSpec and Capybara $ bundle update $ rails g rspec:install
38. Configure RSpec Add to spec_helper.rb, right before RSpec.configure: require 'database_cleaner' require 'spree/core/testing_suppo rt/factories' require 'spree/core/testing_suppo rt/env' require 'spree/core/testing_suppo rt/controller_requests' require 'spree/core/url_helpers'
39. Configure RSpec In spec_helper.rb, change: config.use_transactional_ fixtures = true to: config.use_transactional_ fixtures = false
40. Configure RSpec In spec_helper.rb inside RSpec.configure block, add: config.before(:each) do if example.metadata[:js] DatabaseCleaner.strateg y = :truncation, { :except => [ 'spree_countries', 'spree_zones', 'spree_zone_members', 'spree_states', 'spree_roles' ]} else
41. Configure RSpec In spec_helper.rb inside RSpec.configure block, add: config.before(:each) do DatabaseCleaner.start end config.after(:each) do DatabaseCleaner.clean end
42. Configure RSpec In spec_helper.rb inside RSpec.configure block, add: config.include FactoryGirl::Syntax::Meth ods config.include Spree::Core::UrlHelpers config.include Spree::Core::TestingSup port::ControllerRequests
43. A simple test to make sure it's working spec/requests/home_spec.rb: require 'spec_helper' describe 'home' do it 'should load home page' do visit '/' page.should have_content('Home') end end $ bundle exec rake db:test:prepare $ be rspec
44. Writing an Acceptance Test Example scenario: related products
45. Demo http://github.com/mscottford/sample-store branch: acceptance-test
46. Writing an Integration Test Example scenario: Adding a method to Spree::Product.
47. Demo http://github.com/mscottford/sample-store branch: integration-test
48. Writing a unit test Example scenario: Adding a helper method
49. Testing Spree Stores Summary http://github.com/mscottford/sample-store Getting started - branch: master Acceptance test - branch: acceptance-test Integration test - branch: integration-test Unit test - branch: unit-test
50. Testing Spree Extensions http://github.com/mscottford/spree_sample_extension
51. Getting Started http://github.com/mscottford/spree_sample_extension branch: master $ gem install spree_cmd $ spree extension sample_extension
52. Writing an Acceptance Test Scenario: Special Pricing
53. Demo http://github.com/mscottford/spree_sample_extension branch: acceptance-test
54. Writing an Integration Test Scenario: Special pricing for select products
55. Demo http://github.com/mscottford/spree_sample_extension branch: integration-test
56. Writing a unit test Scenario: Adding a helper to remove duplication
57. Demo http://github.com/mscottford/spree_sample_extension branch: unit-test
58. Testing Spree Extensions Summary http://github.com/mscottford/spree_sample_extension Getting started - branch: master Acceptance test - branch: acceptance-test Integration test - branch: integration-test Unit test - branch: unit-test
59. Testing Spree Stores and Extensions Summary Why Test? Best Practices Testing Spree Stores Testing Spree Extensions
60. Additional resources Read the Spree RSpec tests http://github.com/spree/spree Developing Spree Extension with TDD http://nebulab.it/en/nebulog/developing-spree- extension-with-tdd
61. Additional resources Presentation http://github.com/mscottford/testing-spree-stores- and-extensions Sample Store code http://github.com/mscottford/sample-store Sample Extension code http://github.com/mscottford/spree_sample_extension
62. Contact info email: scott@mscottford.com github: mscottford twitter: @mscottford blog: http://mscottford.com
63. Questions?