blocks|key|1255246|text|通常，我所做的是使用一个别名命令，该命令可以同时运行迁移和准备测试数据库。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1255247|rake+db:migrate+&&+rake+db:test:prepare|code-block|syntax|javascript|1255248|在.bashrc中，只需像这样创建一个别名命令，然后在需要时运行migrate_databases即可。|1255249|alias+migrate_databases='rake+db:migrate+&&+rake+db:test:prepare'|1255250|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

Typically what I do is use an alias command that runs both migrate and prepares the test database.

<pre><code>rake db:migrate &amp;&amp; rake db:test:prepare
</code></pre>

In your .bashrc just create an alias command like so and then run migrate_databases whenever you need to.

<pre><code>alias migrate_databases='rake db:migrate &amp;&amp; rake db:test:prepare'
</code></pre>

blocks|key|3386761|text|我对Rails+4的解决方案是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3386762|在spec/spec_helper.rb中或测试环境初始化代码中的任何位置：|offset|length|style|CODE|3386763|#+Automigrate+if+needs+migration
if+ActiveRecord::Migrator.needs_migration?
++ActiveRecord::Migrator.migrate(File.join(Rails.root,+'db/migrate'))
end|code-block|syntax|javascript|3386764|更新：正如道里安在评论中指出的那样，你不需要单独检查是否有任何未决的迁移，因为ActiveRecord::Migrator.migrate已经在幕后完成了这项工作。所以你可以有效地使用这一行：|BOLD|3386765|ActiveRecord::Migrator.migrate(File.join(Rails.root,+'db/migrate'))|3386766|entityMap^0|0|1|J|0|0|0|3|13|U|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@$D|V|E|W|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|X|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|Y|8|@$D|Z|E|10|F|O]|$D|11|E|12|F|G]]|9|@]|A|$]]|$1|P|3|Q|5|J|7|13|8|@]|9|@]|A|$K|L]]|$1|R|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|S|$]]

My solution for Rails 4:

in <code>spec/spec_helper.rb</code> or anywhere in testing environment initialization code:

<pre><code># Automigrate if needs migration
if ActiveRecord::Migrator.needs_migration?
 ActiveRecord::Migrator.migrate(File.join(Rails.root, 'db/migrate'))
end
</code></pre>

UPD: As Dorian kindly pointed out in comments, you don't need to check separately if there are any pending migrations, because <code>ActiveRecord::Migrator.migrate</code> already does this behind the scenes. So you can effectively use just this one line:

<pre><code>ActiveRecord::Migrator.migrate(File.join(Rails.root, 'db/migrate'))
</code></pre>

blocks|key|506889|text|Rails+4.1向前版本，您可以使用：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|506890|ActiveRecord::Migration.maintain_test_schema!|code-block|syntax|javascript|506891|添加到你的spec_helper.rb或rails_helper.rb的顶部，你就可以开始了。More+info+here。|offset|length|style|CODE|506892|entityMap|0|LINK|mutability|MUTABLE|url|https://www.relishapp.com/rspec/rspec-rails/docs/upgrade#pending-migration-checks^0|0|0|5|E|K|F|1B|E|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|W|8|@$I|X|J|Y|K|L]|$I|Z|J|10|K|L]]|9|@$I|11|J|12|1|13]]|A|$]]|$1|M|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|N|$O|$5|P|Q|R|A|$S|T]]]]

Rails 4.1 forward you can use:

<pre><code>ActiveRecord::Migration.maintain_test_schema!
</code></pre>

Add at the top of your <code>spec_helper.rb</code> or <code>rails_helper.rb</code> and you're good to go. <a href="https://www.relishapp.com/rspec/rspec-rails/docs/upgrade#pending-migration-checks" rel="noreferrer">More info here</a>.

blocks|key|3386718|text|以下是我的解决方法：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3386719|Rakefile：|3386720|require+File.expand_path('../config/application',+__FILE__)
require+'rake'
require+"rspec/core/rake_task"

MyApp::Application.load_tasks

desc+"Run+specs"
RSpec::Core::RakeTask.new(:spec)

task+:run_specs+=>+['db:test:clone',+:spec]+do

end

task+:default+=>+:run_specs|code-block|syntax|javascript|3386721|然后我运行$+rake+run_specs|3386722|出于某种原因，默认任务不会默认为run_specs|3386723|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Here's my workaround:

Rakefile:

<pre><code>require File.expand_path('../config/application', __FILE__)
require 'rake'
require "rspec/core/rake_task"

MyApp::Application.load_tasks

desc "Run specs"
RSpec::Core::RakeTask.new(:spec)

task :run_specs =&gt; ['db:test:clone', :spec] do

end

task :default =&gt; :run_specs
</code></pre>

Then I run $ rake run_specs

for some reason default task doesn't default to run_specs

blocks|key|3386796|text|看看您的spec_helper.rb中是否有以下内容？每次运行specs时，RSpec都会检查是否有挂起的迁移。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3386797|#Checks+for+pending+migrations+before+tests+are+run.
#If+you+are+not+using+ActiveRecord,+you+can+remove+this+line.
ActiveRecord::Migration.check_pending!+if+defined?(ActiveRecord::Migration)|code-block|syntax|javascript|3386798|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

See if you have the following in your spec_helper.rb? Everytime you run specs, RSpec checks if there are pending migrations.

<pre><code>#Checks for pending migrations before tests are run.
#If you are not using ActiveRecord, you can remove this line.
ActiveRecord::Migration.check_pending! if defined?(ActiveRecord::Migration)
</code></pre>

blocks|key|1978829|text|即使在Rails未加载且大多数情况下只执行一个SQL查询的情况下，这也是有效的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1978830|if+defined?(ActiveRecord::Migrator)
++ActiveRecord::Migrator.migrate(File.join(Rails.root,+'db',+'migrate'))
end|code-block|syntax|javascript|1978831|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This works even when Rails is not loaded and only does one SQL query most of the time.

<pre><code>if defined?(ActiveRecord::Migrator)
 ActiveRecord::Migrator.migrate(File.join(Rails.root, 'db', 'migrate'))
end
</code></pre>

I'm developing a Rails application with Rspec for unit testing. 

Weeks ago, Rspec used to migrate the database to the last version automatically when executing 'rake spec', but now it doesn't do it automatically, I have to implement everything for myself.

This happens in test environment, because my development data doesn't desappear.

Is my fault? I didn't change anything, I think :)

Thanks in advance.

MIgrations and Rspec

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我正在使用Rspec开发一个用于单元测试的Rails应用程序。几周前，Rspec在执行'rake spec‘时会自动将数据库迁移到最新版本，但现在它不会自动执行，我必须自己实现所有的功能。这是在测试环境中发生的，因为我的开发数据没有显示出来。是我的错吗？我没有改变任何东西，我想:)提前谢谢。

问MIgrations和Rspec
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MIgrations和RspecEN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问MIgrations和Rspec
EN