blocks|key|3687613|text|为了通过lambda表示法使用隐式主题，您可以执行以下操作：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3687614|describe+"as+an+authenticated+user+that+made+the+offer"+do
++before+{+log_in+offering_user+}
++subject+{+->+{+delete+:destroy,+id:+offer.id+}+}
++it+{+should+change+{Offer.count}.by(-1)+}
end|code-block|syntax|javascript|3687615|我还不知道如何让这个测试变得枯燥:)|3687616|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

In order to use implicit subject with lambda notation you can do the following:

<pre><code>describe "as an authenticated user that made the offer" do
 before { log_in offering_user }
 subject { -&gt; { delete :destroy, id: offer.id } }
 it { should change {Offer.count}.by(-1) }
end
</code></pre>

I don't see yet how to dry up this test :)

blocks|key|1565296|text|如果您不介意重构测试以使用expect语法(recommended)，并在同一个测试中测试多个条件，您可以执行以下操作：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1565297|describe+"as+an+authenticated+user+that+made+the+offer"+do
++let(:destroying_an_offer)+{+->+{+delete+:destroy,+id:+offer.id+}+}
++before+{+log_in+offering_user+}

++it+"destroys+offer"+do
++++expect(destroying_an_offer).to+change(Offer,+:count).by(-1)
++++expect(response).to+redirect_to(item_path(offer.receiving_item))
++++expect(flash[:success]).to_not+be_nil
++end
end|code-block|syntax|javascript|1565298|第一个expect将发出delete请求，其余的expect将在后续操作。|1565299|如果您想使用should语法，我认为您将无法避免多次发出请求，因此很难在您的规范中进一步重构它们。不过，如果您想专门说明受请求影响的应用程序的不同方面，那么您甚至可以为每个规范更改subject，以便根据每个规范获得一个单独的、专注的it块：|1565300|describe+"as+an+authenticated+user+that+made+the+offer"+do
++before+do
++++log_in+offering_user
++++delete+:destroy,+id:+offer.id
++end

++describe+"behaviour"+do
++++subject+{+response+}
++++it+{+should+redirect_to+item_path(offer.receiving_item)+}
++end

++describe+"appearance"+do
++++subject+{+flash[:success]+}
++++it+{+should_not+be_nil+}
++end

++describe+"result"+do
++++subject+{+->+{+delete+:destroy,+id:+offer.id+}+}
++++it+{+should+change(Offer,+:count).by(-1)+}
++end
end|1565301|entityMap|0|LINK|mutability|MUTABLE|url|http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax^0|D|6|M|B|0|0|0|3|6|C|6|O|6|0|6|6|2I|7|39|2|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@$9|11|A|12|1|13]]|E|$]]|$1|F|3|G|5|H|7|14|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|15|8|@$9|16|A|17|B|C]|$9|18|A|19|B|C]|$9|1A|A|1B|B|C]]|D|@]|E|$]]|$1|M|3|N|5|6|7|1C|8|@$9|1D|A|1E|B|C]|$9|1F|A|1G|B|C]|$9|1H|A|1I|B|C]]|D|@]|E|$]]|$1|O|3|P|5|H|7|1J|8|@]|D|@]|E|$I|J]]|$1|Q|3|-4|5|6|7|1K|8|@]|D|@]|E|$]]]|R|$S|$5|T|U|V|E|$W|X]]]]

If you don't mind refactoring your tests to use <code>expect</code> syntax (<a href="http://myronmars.to/n/dev-blog/2012/06/rspecs-new-expectation-syntax" rel="nofollow">recommended</a>), and testing multiple conditions in the same test, you could do the following:

<pre><code>describe "as an authenticated user that made the offer" do
 let(:destroying_an_offer) { -&gt; { delete :destroy, id: offer.id } }
 before { log_in offering_user }

 it "destroys offer" do
 expect(destroying_an_offer).to change(Offer, :count).by(-1)
 expect(response).to redirect_to(item_path(offer.receiving_item))
 expect(flash[:success]).to_not be_nil
 end
end
</code></pre>

The first <code>expect</code> will make the <code>delete</code> request, and the rest of the <code>expect</code>s will operate on the aftermath. 

If you want to use the <code>should</code> syntax, I don't think you'll be able to avoid making the request multiple times, so it'd be difficult to further refactor them out of your specs. As a bit of food for thought though, if you wanted to specifically spec out the different aspects of your app that are affected by the request, you could even do <code>subject</code> changing for each spec in order to get a singular focused <code>it</code> block per spec:

<pre><code>describe "as an authenticated user that made the offer" do
 before do
 log_in offering_user
 delete :destroy, id: offer.id
 end

 describe "behaviour" do
 subject { response }
 it { should redirect_to item_path(offer.receiving_item) }
 end

 describe "appearance" do
 subject { flash[:success] }
 it { should_not be_nil }
 end

 describe "result" do
 subject { -&gt; { delete :destroy, id: offer.id } }
 it { should change(Offer, :count).by(-1) }
 end
end
</code></pre>

I'm pretty sure I can make this test cleaner, been searching all over but can't crack it. The test passes but I would like to refactor.

<pre><code>describe "as an authenticated user that made the offer" do
 before { log_in offering_user; }
 specify { expect { delete :destroy, id: offer.id }.to change(Offer, :count).by(-1) }
 describe "redirect and flash" do
 before { delete :destroy, id: offer.id }
 specify { response.should redirect_to item_path(offer.receiving_item) }
 specify { flash[:success].should_not be_nil }
 end
end
</code></pre>

See how I have had to make the request twice in the spec? It's forced me to use another describe block too. Ideally I could just make the request in the first <code>before</code> block and have something along the lines of

<pre><code>it { should change(Offer, :count).by(-1) }
</code></pre>

Can anyone point me in the right direction? Thanks.

Ruby on Rails - RSpec - Refactoring a lambda style test

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

我很确定我可以让这个测试变得更干净，我到处都在找，但就是不能破解它。测试通过了，但我想重构一下。describe "as an authenticated user that made the offer" do    before { log_in offering_user; }    specify { expe...

问Ruby on Rails - RSpec -重构lambda风格的测试
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Ruby on Rails - RSpec -重构lambda风格的测试EN