blocks|key|4862380|text|Unit和Rspec都是非常好的解决方案。对我来说，我更喜欢在我的Rails项目中使用RSpec+-因为它有许多自动解决方案，比如自动测试，突出显示语法，快捷命令，比如rake+spec，以及其他让测试变得更容易的东西。但是在我的普通ruby脚本中，我使用Test::Unit+-当你不需要复杂的测试(集成测试和其他测试)时，它是非常轻量级和简单的。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|4862381|entityMap^0|2C|9|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

Both Test::Unit and Rspec are very nice solutions. As for me I prefer to use RSpec in my Rails project - because it has many automatic solutions like autotest, highlighting syntax, shortcut commands like <code>rake spec</code> and other stuff that make using test easer. But in my plain ruby scripts I use Test::Unit - it is very lightweight and staightforward when you don't need complex testing (integrational and others)

blocks|key|2789935|text|答案是品味问题，在一个项目中使用这两种方法，然后找到你更喜欢的。(I+do+Test::Unit，RSpec对我来说太甜了)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2789936|MiniTestUpdate2014BDD:由于Ruby2.x内置了MiniTest，我建议您最终检查一下MiniTest，它是一个简单的扩展。您可以混合使用"describe“和"it”块来很好地构建测试上下文。它还提供了"must_be..“如果你想要比assert更多的匹配器。|offset|length|style|BOLD|CODE|2789937|entityMap^0|0|1X|21|3L|6|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@$D|M|E|N|F|G]|$D|O|E|P|F|H]]|9|@]|A|$]]|$1|I|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|J|$]]

The answer is matter of taste, use both in one project and find yourself what do you prefer. (I do Test::Unit, RSpec has to much sugar for me).

Update 2014: As Ruby 2.x has MiniTest built-in I would suggest to check MiniTest::Spec eventually which is simple BDD extension. You can mix "describe" and "it" blocks to nicely structure test contexts with. It also provides "must_be.." matchers if you want to more than <code>assert</code>.

blocks|key|2790080|text|我更喜欢并使用这些gem进行测试。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2790081|2790082|Rspec|unordered-list-item|2790083|Faker+(用于为database)|2790084|Fabrication创建随机且正确的数据(用于简单地创建实例)|2790085|2790086|要开始学习rspec，请看一下这个演示文稿。它包含了所有必要的示例：|2790087|http://kerryb.github.com/iprug-rspec-presentation|offset|length|2790088|也可以通读rspec上的这些文章：|2790089|http://relishapp.com/rspec/rspec-rails|2790090|entityMap|0|LINK|mutability|MUTABLE|url|1^0|0|0|0|0|0|0|0|0|1D|0|0|0|0|12|1|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|14|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|15|8|@]|9|@]|A|$]]|$1|H|3|I|5|E|7|16|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|17|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|18|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|19|8|@]|9|@$O|1A|P|1B|1|1C]]|A|$]]|$1|Q|3|R|5|6|7|1D|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1E|8|@]|9|@$O|1F|P|1G|1|1H]]|A|$]]|$1|U|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|V|$W|$5|X|Y|Z|A|$10|N]]|11|$5|X|Y|Z|A|$10|T]]]]

I prefer and use these gems for testing

<ul>
<li>Rspec</li>
<li>Faker (for creating random and proper data for database)</li>
<li>Fabrication (for simple creating instances)</li>
</ul>

To start with rspec take a look at this presentation. It contains all the necessary examples:

<a href="http://kerryb.github.com/iprug-rspec-presentation" rel="noreferrer">http://kerryb.github.com/iprug-rspec-presentation</a>

Also read through these articles on rspec:

<a href="http://relishapp.com/rspec/rspec-rails" rel="noreferrer">http://relishapp.com/rspec/rspec-rails</a>

blocks|key|3075791|text|测试，特别是如果您遵循链接并阅读评论，提供了对This+Ruby+Inside+article：：Unit和RSpec的相对优点的相当全面的讨论。一个关键的区别似乎是：|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3075792|拥有非技术客户的|3075793|people更倾向于查看测试和Cucumber+more+favourably;|unordered-list-item|style|BOLD|3075794|others更倾向于使用更直接的系统，如：：RSpec。|3075795|3075796|有关RSpec和this+part+of+Michael+Hartl's+Rails+Tutorial的比较，请参阅Cucumber。|3075797|entityMap|0|LINK|mutability|MUTABLE|url|http://www.rubyinside.com/dhh-offended-by-rspec-debate-4610.html|1|http://ruby.railstutorial.org/book/ruby-on-rails-tutorial#sec%253acucumber^0|N|O|0|0|0|0|14|0|0|K|0|0|8|17|1|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@$A|10|B|11|1|12]]|C|$]]|$1|D|3|E|5|6|7|13|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|14|8|@$A|15|B|16|I|J]]|9|@]|C|$]]|$1|K|3|L|5|H|7|17|8|@$A|18|B|19|I|J]]|9|@]|C|$]]|$1|M|3|-4|5|6|7|1A|8|@]|9|@]|C|$]]|$1|N|3|O|5|6|7|1B|8|@]|9|@$A|1C|B|1D|1|1E]]|C|$]]|$1|P|3|-4|5|6|7|1F|8|@]|9|@]|C|$]]]|Q|$R|$5|S|T|U|C|$V|W]]|X|$5|S|T|U|C|$V|Y]]]]

<a href="http://www.rubyinside.com/dhh-offended-by-rspec-debate-4610.html">This Ruby Inside article</a>, especially if you follow the links and read the comments, provides quite a thorough discussion of the relative merits of Test::Unit and RSpec. A key differentiator seems to be that:

<ul>
<li>people who have non-technical clients are more likely to view RSpec and Cucumber more favourably;</li>
<li>others are more likely to prefer more direct systems like Test::Unit.</li>
</ul>

Also see <a href="http://ruby.railstutorial.org/book/ruby-on-rails-tutorial#sec%3acucumber">this part of Michael Hartl's Rails Tutorial</a> for a comparison of RSpec and Cucumber.

blocks|key|2790032|text|如果你有一个大型网站，你可以将rspec与cucumber和webrat+gem结合使用，这是一个很好的组合。它一开始会很麻烦，但以后会有很大的好处。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|2790033|你可以观看下面的铁路广播，了解更多关于这些宝石的信息：|2790034|155以Cucumber开头|2790035|156+Webrat|2790036|157+RSpec匹配器和宏|2790037|关于黄瓜的更多159|2790038|也有一些其他的宝石，如capybara，它是相对较新和有前途的，但老实说，我没有尝试它。|2790039|entityMap^0|F|5|L|8|U|6|0|0|0|0|0|0|B|8|0^^$0|@$1|2|3|4|5|6|7|T|8|@$9|U|A|V|B|C]|$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|10|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|11|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|12|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|13|8|@]|D|@]|E|$]]|$1|N|3|O|5|6|7|14|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|15|8|@$9|16|A|17|B|C]]|D|@]|E|$]]|$1|R|3|-4|5|6|7|18|8|@]|D|@]|E|$]]]|S|$]]

You could use <code>rspec</code> with <code>cucumber</code> and <code>webrat</code> gems which makes a great combination, if you have a large website. It will be cumbersome at first but later on it will be a huge benefit.

You could watch the following railscasts episodes to have more info about those gems: 
155 Beginning with Cucumber 
156 Webrat 
157 RSpec Matchers &amp; Macros 
159 More on Cucumber 

There are also some other gems like <code>capybara</code> which is relatively new and promising, but honestly I didnt try it.

blocks|key|2790110|text|如果你是从测试Rails应用开始你的旅程，我建议你从TestUnit开始。你可以在http://www.codeschool.com/courses/rails-testing-for-zombies上找到关于最佳测试rails应用程序和最佳实践的非常好的课程。如果你在测试方面更有经验，你可以尝试RSpec。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|2790111|entityMap|0|LINK|mutability|MUTABLE|url|http://www.codeschool.com/courses/rails-testing-for-zombies^0|15|1N|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

If you're beginning your journey with testing Rails application I would recommend you start doing it with TestUnit. You can find very nice course about best testing rails app and best practices on <a href="http://www.codeschool.com/courses/rails-testing-for-zombies" rel="nofollow">http://www.codeschool.com/courses/rails-testing-for-zombies</a>
If you're more experienced when it comes to testing you can try RSpec.

I'm beginning the planning phase of creating a testing suite for my rails 3.0.8 application. I'm trying to decide on which testing framework/gems to use. Normally I prefer to stick to Rails convention as much as possible. However, this means using TestUnit. There are many competing test frameworks to choose from that were created as an alternative to TestUnit. Has TestUnit gotten better over the years, or is it not a very good contender? 

I've also heard of a lot of good things about rspec. Are rspec and TestUnit close in terms of functionality, or does rspec blow TestUnit out of the water?

Whatever framework I choose, I'd prefer it to have a good support base(lots of users and documentation), ease of use/simplicity, and a lasting future.

Rspec vs. TestUnit

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在开始为我的rails 3.0.8应用程序创建测试套件的规划阶段。我正在尝试决定使用哪种测试框架/gem。通常，我更喜欢尽可能多地遵循Rails约定。然而，这意味着要使用TestUnit。有许多竞争的测试框架可供选择，它们是作为TestUnit的替代品而创建的。这些年来，TestUnit是变得更好了，还是说它不是一个很好的竞争者？我也听说过很多关于rspec的好消息。rspec和TestUni

问Rspec与TestUnit
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Rspec与TestUnitEN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Rspec与TestUnit
EN