当我运行测试时,如何让Rails加载我的测试环境变量?

时间:2017-09-23 18:42:47

标签: ruby-on-rails testing environment-variables ruby-on-rails-5 minitest

我正在使用Rails 5.我有这个文件,config / environment_variables.yml

development:
  COINBASE_KEY: devkey
  COINBASE_SECRET: devsecret
test:
  COINBASE_KEY: testkey
  COINBASE_SECRET: testsecret
production:
  COINBASE_KEY: prodkey
  COINBASE_SECRET: prodsecret

我用文件config / initializers / environment_variables.rb

加载它
module EnvironmentVariables
  class Application < Rails::Application
    config.before_configuration do
      env_file = Rails.root.join("config", 'environment_variables.yml').to_s

      if File.exists?(env_file)
        YAML.load_file(env_file)[Rails.env].each do |key, value|
          ENV[key.to_s] = value
        end # end YAML.load_file
      end # end if File.exists?
    end # end config.before_configuration
  end # end class
end # end module

但是当我使用

运行我的测试时
rails test test/services/crypto_currency_service_test.rb

测试变量不是加载 - 而是来自开发环境的加载。以下是我的测试文件

require 'coinbase/wallet'
require 'minitest/mock'

class CryptoCurrencyServiceTest <  ActiveSupport::TestCase

  test 'sell' do
    last_transaction = MyTransaction.new({
      :transaction_type => "buy",
      :amount_in_usd => "100",
      :btc_price_in_usd => "3000"
    })

    puts "env: #{ENV['COINBASE_KEY']}"
    @client = Coinbase::Wallet::Client.new(api_key: ENV['COINBASE_KEY'], api_secret: ENV['COINBASE_SECRET'])

运行测试时,如何在默认情况下加载测试变量?

编辑:这是config / environments / test.rb文件,我没有(有意识地)改变了......

Rails.application.configure do
  # Settings specified here will take precedence over those in config/application.rb.

  # The test environment is used exclusively to run your application's
  # test suite. You never need to work with it otherwise. Remember that
  # your test database is "scratch space" for the test suite and is wiped
  # and recreated between test runs. Don't rely on the data there!
  config.cache_classes = true

  # Do not eager load code on boot. This avoids loading your whole application
  # just for the purpose of running a single test. If you are using a tool that
  # preloads Rails for running tests, you may have to set it to true.
  config.eager_load = false

  # Configure public file server for tests with Cache-Control for performance.
  config.public_file_server.enabled = true
  config.public_file_server.headers = {
    'Cache-Control' => 'public, max-age=3600'
  }

  # Show full error reports and disable caching.
  config.consider_all_requests_local       = true
  config.action_controller.perform_caching = false

  # Raise exceptions instead of rendering exception templates.
  config.action_dispatch.show_exceptions = false

  # Disable request forgery protection in test environment.
  config.action_controller.allow_forgery_protection = false
  config.action_mailer.perform_caching = false

  # Tell Action Mailer not to deliver emails to the real world.
  # The :test delivery method accumulates sent emails in the
  # ActionMailer::Base.deliveries array.
  config.action_mailer.delivery_method = :test

  # Print deprecation notices to the stderr.
  config.active_support.deprecation = :stderr

  # Raises error for missing translations
  # config.action_view.raise_on_missing_translations = true
end

2 个答案:

答案 0 :(得分:5)

我不建议为此编写自定义代码。存在用于设置环境变量的现有解决方案。例如,请参阅dotenv-rails。它允许您将公共变量放入.env文件中。只需将gem 'dotenv-rails'添加到Gemfile并将常用变量放入.env文件中:

# .env
COINBASE_KEY: devkey
COINBASE_SECRET: devsecret

如果您需要特定于环境的变量,则可以为此设置单独的文件:.env.development.env.test.env.production

#.env.test

COINBASE_KEY: testkey
COINBASE_SECRET: testsecret


#.env.production

COINBASE_KEY: prodkey
COINBASE_SECRET: prodsecret

答案 1 :(得分:0)

根据原帖中的评论,我建议检查config.before_configuration块是否有错。在该块运行之后可能会加载rails环境,因此当您在测试中打印出来时会得到Rails.env == 'test',但在配置中它会从默认(开发)环境中获取密钥。

我建议移动这部分

env_file = Rails.root.join("config", 'environment_variables.yml').to_s

      if File.exists?(env_file)
        YAML.load_file(env_file)[Rails.env].each do |key, value|
          ENV[key.to_s] = value
        end # end YAML.load_file
      end # end if File.exists?

在一个初始化器中,然后检查环境变量。可能会解决问题。 (因为初始化者肯定应该尊重环境)

更新:从documentation开始before_configuration块似乎是第一个要运行的第一个块配置部分,因此Rails.env可能尚未设置。