blocks|key|966609|text|你的应用应该是类名，例如，而不是：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|966610|def+app
++MainAppLogic.new
end|code-block|syntax|javascript|966611|你必须使用|966612|def+app
++MainAppLogic
end|966613|您不需要指定执行get的端口，因为rack应用程序在测试的上下文中运行；因此这应该是正确的方式：|offset|length|style|CODE|966614|it+"starts+a+server+when+initialized"+do
++++get+"/"
++++last_response.body.should+be+!=+nil
end|966615|此外，由于建议使用新的expect格式而不是should，请参见http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/|966616|和你的MainAppLogic，应该是这样的：|966617|class+MainAppLogic+<+Sinatra::Base
++get+'/'+do
++++'Hello+world'
++end
end|966618|entityMap|0|LINK|mutability|MUTABLE|url|http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/^0|0|0|0|0|8|3|0|0|B|6|M|6|W|1P|0|0|3|C|0|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|17|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|18|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|19|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|1A|8|@$M|1B|N|1C|O|P]]|9|@]|A|$]]|$1|Q|3|R|5|D|7|1D|8|@]|9|@]|A|$E|F]]|$1|S|3|T|5|6|7|1E|8|@$M|1F|N|1G|O|P]|$M|1H|N|1I|O|P]]|9|@$M|1J|N|1K|1|1L]]|A|$]]|$1|U|3|V|5|6|7|1M|8|@$M|1N|N|1O|O|P]]|9|@]|A|$]]|$1|W|3|X|5|D|7|1P|8|@]|9|@]|A|$E|F]]|$1|Y|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]]]

Your app should be the class name, for example instead of:

<pre><code>def app
 MainAppLogic.new
end
</code></pre>

You have to use

<pre><code>def app
 MainAppLogic
end
</code></pre>

You shouldn't need to indicate the port for doing the <code>get</code>, because the rack app runs in the context of the tests; so this should be right way:

<pre><code>it "starts a server when initialized" do
 get "/"
 last_response.body.should be != nil
end
</code></pre>

Also, as a recommendation prefer to use the new <code>expect</code> format instead of the <code>should</code>, see <a href="http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/" rel="nofollow">http://rspec.info/blog/2012/06/rspecs-new-expectation-syntax/</a>

And your <code>MainAppLogic</code>, should be something like:

<pre><code>class MainAppLogic &lt; Sinatra::Base
 get '/' do
 'Hello world'
 end
end
</code></pre>

blocks|key|966597|text|第一件事:为什么要使用自定义类来运行应用程序？您可以使用rackup工具，它是运行机架应用程序的事实标准。关于它的更多细节，here。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|966598|然后你的应用程序代码就变成了：|966599|class+App
++def+call(env)
++++return+[200,+{},+['Hello,+World!']]
++end
end|code-block|syntax|javascript|966600|并使用config.ru|966601|require_relative+'app'

run+App.new|966602|您可以通过运行项目目录中的rackup来启动该应用程序。|966603|至于错误，信息很清楚。rack-test期望app方法的返回值是rack应用程序的实例(响应call方法的对象)。看看rack-test内部发生了什么(作为提示，很容易理解-按照给定的顺序关注它们：lib/rack/test/methods.rb#L30+lib/rack/mock_session.rb#L7+lib/rack/test.rb#L244+lib/rack/mock_session.rb#L30。注意Rack::MockSession是如何实例化的，如何在处理请求时使用它(例如，当您在测试中调用get方法时)，最后是如何在您的应用程序上执行call方法。|966604|我希望现在已经清楚了为什么测试应该看起来像这样(是的，在执行测试时不需要运行服务器)：|966605|describe+App+do
++def+app
++++App.new
++end

++it+"does+a+triple+backflip"+do
++++get+"/"
++++expect(last_response.body).to+eq("Hello,+World")
++end
end|966606|附注:很抱歉链接到rack-test的形式，我当前的分数不能超过2+:P|966607|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/rack/rack/wiki/(tutorial)-rackup-howto)^0|S|6|1Q|4|0|0|0|0|3|9|0|0|D|6|0|B|9|M|3|1A|4|1N|9|2R|S|3K|R|4C|L|4Y|S|5T|H|75|3|7S|4|0|0|0|9|9|0^^$0|@$1|2|3|4|5|6|7|18|8|@$9|19|A|1A|B|C]]|D|@$9|1B|A|1C|1|1D]]|E|$]]|$1|F|3|G|5|6|7|1E|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|1F|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1G|8|@$9|1H|A|1I|B|C]]|D|@]|E|$]]|$1|O|3|P|5|J|7|1J|8|@]|D|@]|E|$K|L]]|$1|Q|3|R|5|6|7|1K|8|@$9|1L|A|1M|B|C]]|D|@]|E|$]]|$1|S|3|T|5|6|7|1N|8|@$9|1O|A|1P|B|C]|$9|1Q|A|1R|B|C]|$9|1S|A|1T|B|C]|$9|1U|A|1V|B|C]|$9|1W|A|1X|B|C]|$9|1Y|A|1Z|B|C]|$9|20|A|21|B|C]|$9|22|A|23|B|C]|$9|24|A|25|B|C]|$9|26|A|27|B|C]|$9|28|A|29|B|C]]|D|@]|E|$]]|$1|U|3|V|5|6|7|2A|8|@]|D|@]|E|$]]|$1|W|3|X|5|J|7|2B|8|@]|D|@]|E|$K|L]]|$1|Y|3|Z|5|6|7|2C|8|@$9|2D|A|2E|B|C]]|D|@]|E|$]]|$1|10|3|-4|5|6|7|2F|8|@]|D|@]|E|$]]]|11|$12|$5|13|14|15|E|$16|17]]]]

First thing: why the custom class to run the app? You can use the <code>rackup</code> tool, which is the de-facto standard for running Rack apps. Some more details on it <a href="https://github.com/rack/rack/wiki/(tutorial)-rackup-howto" rel="nofollow">here</a>.

Your app code then becomes:

<pre><code>class App
 def call(env)
 return [200, {}, ['Hello, World!']]
 end
end
</code></pre>

and with the <code>config.ru</code>

<pre><code>require_relative 'app'

run App.new
</code></pre>

you can start the app by running <code>rackup</code> in your project's directory.

As for the error, the message is pretty clear. <code>rack-test</code> expects, that the return value of <code>app</code> method would be an instance of a rack app (an object that responds to <code>call</code> method). Take a look what happens in <code>rack-test</code> internals (it's pretty easy to follow, as a tip—focus on these in given order: <code>lib/rack/test/methods.rb#L30</code> <code>lib/rack/mock_session.rb#L7</code> <code>lib/rack/test.rb#L244</code> <code>lib/rack/mock_session.rb#L30</code>. Notice how the <code>Rack::MockSession</code> is instantiated, how it is used when processing requests (e.g. when you call <code>get</code> method in your tests) and finally how the <code>call</code> method on your app is executed.

I hope that now it's clear why the test should look more like this (yes, you don't need to have a server running when executing your tests):

<pre><code>describe App do
 def app
 App.new
 end

 it "does a triple backflip" do
 get "/"
 expect(last_response.body).to eq("Hello, World")
 end
end
</code></pre>

P.S.
Sorry for the form of links to <code>rack-test</code>, can't add more than 2 with my current points :P

Here is my rack application:

<pre><code>class MainAppLogic
 def initialize
 Rack::Server.start(:app =&gt;Server, :server =&gt; "WEBrick", :Port =&gt; "8080")
 end
end

class Server
 def self.call(env)
 return [200, {},["Hello, World"]]
 end
end
</code></pre>

When actually run, it behaves as it should and returns "Hello World" to all requests. I'm having trouble convincing rack-test to work with it. Here are my tests:

<pre><code>require "rspec"
require "rack/test"
require "app"

# Rspec config source: https://github.com/shiroyasha/sinatra_rspec 
RSpec.configure do |config|
 config.include Rack::Test::Methods
end

describe MainAppLogic do

 # App method source: https://github.com/shiroyasha/sinatra_rspec
 def app
 MainAppLogic.new
 end

 it "starts a server when initialized" do
 get "/", {}, "SERVER_PORT" =&gt; "8080"
 last_response.body.should be != nil
 end
end
</code></pre>

When I test this, it fails complaining that <code>MainAppLogic</code> is not a rack server, specifically, that it doesn't respond to <code>MainAppLogic.call</code>. How can I let it know to ignore that <code>MainAppLogic</code> isn't a rack server and just place a request to <code>localhost:8080</code>, because there server has started?

Configuring rack-test to start the server indirectly

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

下面是我的机架应用程序：class MainAppLogic    def initialize        Rack::Server.start(:app =>Server, :server => "WEBrick", :Port => "8080")    endendclass Server    def se...

问配置机架测试以间接启动服务器
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问配置机架测试以间接启动服务器EN