# By placing all of Spree's shared dependencies in this file and then loading
# it for each component's Gemfile, we can be sure that we're only testing just
# the one component of Spree.
source 'https://rubygems.org'

platforms :ruby do
  gem 'mysql2'
  gem 'pg'
  gem 'sqlite3'
  gem 'fast_sqlite'
end

platforms :jruby do
  gem 'jruby-openssl'
  gem 'activerecord-jdbcsqlite3-adapter'
end

gem 'coffee-rails'
gem 'sass-rails'

group :test do
  gem 'capybara', '~> 2.4'
  gem 'capybara-screenshot'
  gem 'database_cleaner', '~> 1.3'
  gem 'email_spec'
  gem 'factory_girl_rails', '~> 4.5.0'
  gem 'launchy'
  gem 'rspec-activemodel-mocks', '~>1.0.2'
  gem 'rspec-collection_matchers'
  gem 'rspec-its'
  gem 'rspec-rails', '~> 3.4.1'
  gem 'simplecov'
  gem 'poltergeist', '~> 1.9'
  gem 'timecop'
  gem 'with_model'
  gem 'rspec_junit_formatter'
end

group :test, :development do
  gem 'rubocop'
  platforms :mri do
    gem 'pry-byebug', '~> 1.0'
  end
end

# By placing all of Spree's shared dependencies in this file and then loading
# it for each component's Gemfile, we can be sure that we're only testing just
# the one component of Spree.
source 'https://rubygems.org'

platforms :ruby do
  gem 'mysql2'
  gem 'pg'
  gem 'sqlite3'
  gem 'fast_sqlite'
end

platforms :jruby do
  gem 'jruby-openssl'
  gem 'activerecord-jdbcsqlite3-adapter'
end

gem 'coffee-rails'
gem 'sass-rails'

group :test do
  gem 'capybara', '~> 2.4'
  gem 'capybara-screenshot'
  gem 'database_cleaner', '~> 1.3'
  gem 'email_spec'
  gem 'factory_girl_rails', '~> 4.5.0'
  gem 'launchy'
  gem 'rspec-activemodel-mocks', '~>1.0.2'
  gem 'rspec-collection_matchers'
  gem 'rspec-its'
  gem 'rspec-rails', '~> 3.4.1'
  gem 'simplecov'
  gem 'poltergeist', '~> 1.9'
  gem 'timecop'
  gem 'with_model'
  gem 'rspec_junit_formatter'
end

group :test, :development do
  gem 'rubocop'
  gem 'pry'

  platforms :mri do
    gem 'byebug'
  end
end

Include pry and byebug, but not pry-byebug
Include pry and byebug, but not pry-byebug

Previously we were using pry-byebug ~> 1.0 to avoid behaviour of newer
byebug versions which locks all threads when the debugger is entered.
This made debugging and developing feature specs impossible.

See https://github.com/deivid-rodriguez/byebug/issues/193

I believe this gives us the best of both worlds, when we want a debugger
capable of stepping through code we can invoke byebug. When we want an
interactive REPL, we can invoke pry.
