blocks|key|448161|text|摘要|type|unstyled|depth|inlineStyleRanges|entityRanges|data|448162|大多数食谱都没有经过测试。在临时服务器上测试部署。|448163|详细信息|448164|大多数食谱都没有经过测试。|448165|according+to+Lee+Hambley+(a+Capistrano+maintainer)的原因是：|offset|length|448166|448167|Capistrano是在测试文化开发之前构建的|ordered-list-item|448168|测试用例的规范与将针对其执行的服务器环境不同。|448169|448170|此外：|448171|448172|Capistranoorb+main+webpage+does+not+mention+it.+|unordered-list-item|448173|除了last+commit+was+2014之外，还有capistrano-spec。|448174|我的项目中的Capistrano+Gem没有测试。|448175|Capistrano-bundler|448176|Capistrano-db-tasks+-测试stubs|448177|Capistrano-postgresql|448178|Capistrano-rails|448179|Capistrano-rails-collection|448180|Capistrano-rails-console|448181|Capistrano-secrets-yml|448182|Capistrano-ssy-doctor|448183|Capistrano-puma|448184|448185|448186|​|448187|我们的建议是，在使用生产环境之前，要有一个测试环境来“测试”。|448188|entityMap|0|LINK|mutability|MUTABLE|url|https://groups.google.com/forum/#!topic/capistrano/Ewc9pZxFR40|1|http://capistranorb.com/|2|https://github.com/technicalpickles/capistrano-spec|3|https://github.com/capistrano/bundler|4|https://github.com/sgruhier/capistrano-db-tasks|5|https://github.com/capistrano-plugins/capistrano-postgresql|6|https://github.com/capistrano/rails|7|https://github.com/dei79/capistrano-rails-collection|8|https://github.com/ydkn/capistrano-rails-console|9|https://github.com/capistrano-plugins/capistrano-secrets-yml|10|https://github.com/capistrano-plugins/capistrano-ssh-doctor|11|https://github.com/seuros/capistrano-puma^0|0|0|0|0|0|1E|0|0|0|0|0|0|0|0|0|1B|1|0|2|K|2|0|1|0|I|3|1|0|J|4|1|0|L|5|1|0|G|6|1|0|R|7|1|0|O|8|1|0|M|9|1|0|L|A|1|0|F|B|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|2K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|2L|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|2M|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|2N|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|2O|8|@]|9|@$J|2P|K|2Q|1|2R]]|A|$]]|$1|L|3|-4|5|6|7|2S|8|@]|9|@]|A|$]]|$1|M|3|N|5|O|7|2T|8|@]|9|@]|A|$]]|$1|P|3|Q|5|O|7|2U|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|2V|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|2W|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|2X|8|@]|9|@]|A|$]]|$1|V|3|W|5|X|7|2Y|8|@]|9|@$J|2Z|K|30|1|31]]|A|$]]|$1|Y|3|Z|5|X|7|32|8|@]|9|@$J|33|K|34|1|35]]|A|$]]|$1|10|3|11|5|X|7|36|8|@]|9|@]|A|$]]|$1|12|3|13|5|O|7|37|8|@]|9|@$J|38|K|39|1|3A]]|A|$]]|$1|14|3|15|5|O|7|3B|8|@]|9|@$J|3C|K|3D|1|3E]]|A|$]]|$1|16|3|17|5|O|7|3F|8|@]|9|@$J|3G|K|3H|1|3I]]|A|$]]|$1|18|3|19|5|O|7|3J|8|@]|9|@$J|3K|K|3L|1|3M]]|A|$]]|$1|1A|3|1B|5|O|7|3N|8|@]|9|@$J|3O|K|3P|1|3Q]]|A|$]]|$1|1C|3|1D|5|O|7|3R|8|@]|9|@$J|3S|K|3T|1|3U]]|A|$]]|$1|1E|3|1F|5|O|7|3V|8|@]|9|@$J|3W|K|3X|1|3Y]]|A|$]]|$1|1G|3|1H|5|O|7|3Z|8|@]|9|@$J|40|K|41|1|42]]|A|$]]|$1|1I|3|1J|5|O|7|43|8|@]|9|@$J|44|K|45|1|46]]|A|$]]|$1|1K|3|-4|5|6|7|47|8|@]|9|@]|A|$]]|$1|1L|3|-4|5|6|7|48|8|@]|9|@]|A|$]]|$1|1M|3|1N|5|6|7|49|8|@]|9|@]|A|$]]|$1|1O|3|1P|5|6|7|4A|8|@]|9|@]|A|$]]|$1|1Q|3|-4|5|6|7|4B|8|@]|9|@]|A|$]]]|1R|$1S|$5|1T|1U|1V|A|$1W|1X]]|1Y|$5|1T|1U|1V|A|$1W|1Z]]|20|$5|1T|1U|1V|A|$1W|21]]|22|$5|1T|1U|1V|A|$1W|23]]|24|$5|1T|1U|1V|A|$1W|25]]|26|$5|1T|1U|1V|A|$1W|27]]|28|$5|1T|1U|1V|A|$1W|29]]|2A|$5|1T|1U|1V|A|$1W|2B]]|2C|$5|1T|1U|1V|A|$1W|2D]]|2E|$5|1T|1U|1V|A|$1W|2F]]|2G|$5|1T|1U|1V|A|$1W|2H]]|2I|$5|1T|1U|1V|A|$1W|2J]]]]

<h3>Summary</h3>

Most recipes are not tested. Test deployments on a staging server.

<h3>Detail</h3>

Most recipes are not tested.

The reason <a href="https://groups.google.com/forum/#!topic/capistrano/Ewc9pZxFR40" rel="nofollow noreferrer">according to Lee Hambley (a Capistrano maintainer)</a> is that:

<ol>
<li>Capistrano was architectured before the testing culture developed</li>
<li>Test cases in a spec do not resemble the server environment that will be executed against.</li>
</ol>

In addition: 

<ul>
<li><a href="http://capistranorb.com/" rel="nofollow noreferrer">Capistranoorb main webpage does not mention it.</a> </li>
<li>There is a capistrano-spec but the <a href="https://github.com/technicalpickles/capistrano-spec" rel="nofollow noreferrer">last commit was 2014</a>. </li>
<li>The Capistrano Gems in my project have no tests. 

<ol>
<li><a href="https://github.com/capistrano/bundler" rel="nofollow noreferrer">Capistrano-bundler</a></li>
<li><a href="https://github.com/sgruhier/capistrano-db-tasks" rel="nofollow noreferrer">Capistrano-db-tasks</a> - test stubs</li>
<li><a href="https://github.com/capistrano-plugins/capistrano-postgresql" rel="nofollow noreferrer">Capistrano-postgresql</a></li>
<li><a href="https://github.com/capistrano/rails" rel="nofollow noreferrer">Capistrano-rails</a></li>
<li><a href="https://github.com/dei79/capistrano-rails-collection" rel="nofollow noreferrer">Capistrano-rails-collection</a></li>
<li><a href="https://github.com/ydkn/capistrano-rails-console" rel="nofollow noreferrer">Capistrano-rails-console</a></li>
<li><a href="https://github.com/capistrano-plugins/capistrano-secrets-yml" rel="nofollow noreferrer">Capistrano-secrets-yml</a></li>
<li><a href="https://github.com/capistrano-plugins/capistrano-ssh-doctor" rel="nofollow noreferrer">Capistrano-ssy-doctor</a></li>
<li><a href="https://github.com/seuros/capistrano-puma" rel="nofollow noreferrer">Capistrano-puma</a></li>
</ol></li>
</ul>

The advice is to have a staging environment to 'test' against before using production.

blocks|key|347005|text|Capistrano项目本身确实具有测试文化，并且包括使用Vagrant+VM代替远程服务器的integration+tests+(黄瓜“特性”)。这些测试运行起来有些慢，需要特殊的工具(例如Virtual+Box)，并且在Travis+CI中不起作用。因此，这种风格的集成测试从未在更广泛的Capistrano第三方gem社区中流行起来。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|347006|然而，Capistrano最近对formalize+its+plugin+system进行了改进，使这些插件更容易进行单元测试。例如，内置到Capistrano中的SCM实现现在都是use+this+new+plugin+system，并有相应的测试。|347007|我希望新的Capistrano+gem能够利用插件架构并提供更好的测试。如果您正计划编写自己的Capistrano任务库，可以使用refer+to+the+SCM+tests来测试策略，并随时提出改进建议。|347008|如果您不是在开发gem，而是简单地使用Capistrano来部署应用程序:基于各种Capistrano+gem、配置、服务器环境等的组合，您的部署对于您的特定项目将是唯一的。|347009|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/capistrano/capistrano/tree/26cf534987f8ed4d58382cdab7077e0c09700e0f/features|1|https://github.com/capistrano/capistrano/blob/26cf534987f8ed4d58382cdab7077e0c09700e0f/lib/capistrano/plugin.rb|2|https://github.com/capistrano/capistrano/blob/26cf534987f8ed4d58382cdab7077e0c09700e0f/lib/capistrano/scm/git.rb|3|https://github.com/capistrano/capistrano/blob/26cf534987f8ed4d58382cdab7077e0c09700e0f/spec/lib/capistrano/scm/git_spec.rb^0|1B|H|0|0|G|R|1|2J|Q|2|0|1T|M|3|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@$A|Y|B|Z|1|10]]|C|$]]|$1|D|3|E|5|6|7|11|8|@]|9|@$A|12|B|13|1|14]|$A|15|B|16|1|17]]|C|$]]|$1|F|3|G|5|6|7|18|8|@]|9|@$A|19|B|1A|1|1B]]|C|$]]|$1|H|3|I|5|6|7|1C|8|@]|9|@]|C|$]]|$1|J|3|-4|5|6|7|1D|8|@]|9|@]|C|$]]]|K|$L|$5|M|N|O|C|$P|Q]]|R|$5|M|N|O|C|$P|S]]|T|$5|M|N|O|C|$P|U]]|V|$5|M|N|O|C|$P|W]]]]

The Capistrano project itself does have a testing culture and includes <a href="https://github.com/capistrano/capistrano/tree/26cf534987f8ed4d58382cdab7077e0c09700e0f/features" rel="nofollow noreferrer">integration tests</a> (Cucumber "features") that use a Vagrant VM to take the place of a remote server. These tests are somewhat slow to run, require special tools (e.g. Virtual Box), and do not work in Travis CI. Hence this style of integration testing has never caught on with the wider Capistrano community of third-party gems.

However, Capistrano has recently made improvements to <a href="https://github.com/capistrano/capistrano/blob/26cf534987f8ed4d58382cdab7077e0c09700e0f/lib/capistrano/plugin.rb" rel="nofollow noreferrer">formalize its plugin system</a> and to make these plugins easier to unit test. For example, the SCM implementations built into Capistrano now all <a href="https://github.com/capistrano/capistrano/blob/26cf534987f8ed4d58382cdab7077e0c09700e0f/lib/capistrano/scm/git.rb" rel="nofollow noreferrer">use this new plugin system</a>, and have corresponding tests.

My hope is that new Capistrano gems will take advantage of the plugin architecture and provide better tests. If you are planning on writing your own Capistrano task libraries, <a href="https://github.com/capistrano/capistrano/blob/26cf534987f8ed4d58382cdab7077e0c09700e0f/spec/lib/capistrano/scm/git_spec.rb" rel="nofollow noreferrer">refer to the SCM tests</a> for testing strategies, and feel free to suggest improvements.

If you are not developing a gem, but simply using Capistrano to deploy an application: Your deployment will be unique to your particular project, based on a combination of various Capistrano gems, configuration, server environment, etc. The only real way to test your deployment is by using a staging environment.

Ruby has a testing culture. So I was surprised to find that there were no testing details about Capistrano. 

What are the options for testing Capistrano deploys and Gems?

Testing Capistrano deployments and Gems

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

Ruby有一种测试文化。所以我很惊讶地发现没有关于Capistrano的测试细节。测试Capistrano部署和Gem的选项有哪些？

问测试Capistrano部署和Gems
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问测试Capistrano部署和GemsEN