blocks|key|606744|text|您必须遵守Gatling+API。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|606745|通过检查，您不会“失败”测试，而是请求。如果您希望整个测试失败，您应该看看断言+API和Jenkins插件。|ordered-list-item|offset|length|606746|您只能在请求站点执行检查，而不是稍后执行检查。其中一个很好的原因是，如果您像您正在做的那样将bodyString存储在会话中，那么您将结束使用大量内存，可能会崩溃(仍然引用，而不是垃圾收集)。您必须在检查中执行processData，通常在转换可选步骤中执行。|style|CODE|606747|entityMap|0|LINK|mutability|MUTABLE|url|http://gatling.io/docs/2.0.0-RC3/general/assertions.html?highlight=assertions|1|https://wiki.jenkins-ci.org/display/JENKINS/Gatling%2BPlugin|2|http://gatling.io/docs/2.0.0-RC3/http/http_check.html?highlight=transforming#transforming^0|0|11|2|0|18|9|1|0|2X|B|3C|2|2|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@$E|Y|F|Z|1|10]|$E|11|F|12|1|13]]|A|$]]|$1|G|3|H|5|D|7|14|8|@$E|15|F|16|I|J]]|9|@$E|17|F|18|1|19]]|A|$]]|$1|K|3|-4|5|6|7|1A|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]|S|$5|N|O|P|A|$Q|T]]|U|$5|N|O|P|A|$Q|V]]]]

You have to abide by Gatling APIs.

<ol>
<li>With checks, you don't "fail" the test, but the request. If you're looking for failing the whole test, you should have a look at the <a href="http://gatling.io/docs/2.0.0-RC3/general/assertions.html?highlight=assertions" rel="noreferrer">Assertions</a> API and the <a href="https://wiki.jenkins-ci.org/display/JENKINS/Gatling+Plugin" rel="noreferrer">Jenkins plugin</a>.</li>
<li>You can only perform a Check at the request site, not later. One of the very good reasons is that if you store the bodyString in the Sessions like you're doing, you'll end using a lot of memory and maybe crashing (still referenced, so not garbage collectable). You have to perform your <code>processData</code> in the check, typically in the <a href="http://gatling.io/docs/2.0.0-RC3/http/http_check.html?highlight=transforming#transforming" rel="noreferrer">transform</a> optional step.</li>
</ol>

blocks|key|604963|text|你是在找像|type|unstyled|depth|inlineStyleRanges|entityRanges|data|604964|++.exec(http("getRequest")
++++.get("/request/123")
++++.headers(headers)
++++.check(status.is(200))
++++.check(jsonPath("$.request_id").is("123")))|code-block|syntax|javascript|604965|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|$]]

were you looking for something like 

<pre><code> .exec(http("getRequest")
 .get("/request/123")
 .headers(headers)
 .check(status.is(200))
 .check(jsonPath("$.request_id").is("123")))
</code></pre>

blocks|key|606749|text|我使用exitHereIfFailed实现了一些听起来与您想要完成的任务完全相同的东西。我通常在虚拟用户尝试登录后使用这个。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|606750|exitHereIfFailed就是这样使用的|606751|val+scn+=+scenario("MyAwesomeScenario")
.exec(http("Get+data+from+endpoint+1")
++.get(request1Url)
++.check(status.is(200))
++.check(bodyString.saveAs("MyData"))
++.check(processData(session.attributes("MyData")).is(true)))
.exitHereIfFailed+//+If+we+weren't+able+to+get+the+data,+don't+continue
.exec(http("Send+the+data+to+endpoint+2")
++.post(request2Url)
++.body(StringBody("${MyData}"))|code-block|syntax|javascript|606752|如果exitHereIfFailed之前的任何检查失败，此场景将在exitHereIfFailed上优雅地中止。|606753|entityMap|0|LINK|mutability|MUTABLE|url|https://gatling.io/docs/3.3/cheat-sheet/|1^0|3|G|3|G|0|0|0|G|0|G|1|0|0|2|G|X|G|0^^$0|@$1|2|3|4|5|6|7|X|8|@$9|Y|A|Z|B|C]]|D|@$9|10|A|11|1|12]]|E|$]]|$1|F|3|G|5|6|7|13|8|@$9|14|A|15|B|C]]|D|@$9|16|A|17|1|18]]|E|$]]|$1|H|3|I|5|J|7|19|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|1A|8|@$9|1B|A|1C|B|C]|$9|1D|A|1E|B|C]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]|W|$5|R|S|T|E|$U|V]]]]

I implemented something using <a href="https://gatling.io/docs/3.3/cheat-sheet/" rel="nofollow noreferrer"><code>exitHereIfFailed</code></a> that sounds like exactly what you were trying to accomplish. I normally use this after a virtual user attempts to sign in.

<a href="https://gatling.io/docs/3.3/cheat-sheet/" rel="nofollow noreferrer"><code>exitHereIfFailed</code></a> is used this way

<pre><code>val scn = scenario("MyAwesomeScenario")
.exec(http("Get data from endpoint 1")
 .get(request1Url)
 .check(status.is(200))
 .check(bodyString.saveAs("MyData"))
 .check(processData(session.attributes("MyData")).is(true)))
.exitHereIfFailed // If we weren't able to get the data, don't continue
.exec(http("Send the data to endpoint 2")
 .post(request2Url)
 .body(StringBody("${MyData}"))
</code></pre>

This scenario will abort gracefully at <code>exitHereIfFailed</code> if any of the checks prior to <code>exitHereIfFailed</code> have failed.

blocks|key|296191|text|因为编辑队列已经满了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|296192|这个问题已经在新版本的Gatling中解决了。3.4.0版|296193|他们补充说|296194|exitHereIf|offset|length|296195|exitHereIf("${myBoolean}")
exitHereIf(session+=>+true)|code-block|syntax|javascript|296196|如果条件保持不变，让用户退出这个场景。条件参数是ExpressionBoolean。|296197|entityMap|0|LINK|mutability|MUTABLE|url|https://gatling.io/docs/current/general/scenario/#exithereif^0|0|0|0|0|A|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|10|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|11|8|@]|9|@$H|12|I|13|1|14]]|A|$]]|$1|J|3|K|5|L|7|15|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|16|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

Since the edit queue is already full.
This is already resolved in the new version of Gatling. Release 3.4.0
They added
<a href="https://gatling.io/docs/current/general/scenario/#exithereif" rel="nofollow noreferrer">exitHereIf</a>
<pre><code>exitHereIf(&quot;${myBoolean}&quot;)
exitHereIf(session =&gt; true)
</code></pre>
Make the user exit the scenario from this point if the condition holds. Condition parameter is an Expression[Boolean].

A Gatling scenario with an exec chain. After a request, returned data is saved. Later it's processed and depending on the processing result, it should either fail or pass the test.

This seems like the simplest possible scenario, yet I can't find any reliable info how to fail a test from within an exec block. assert breaks the scenario and seemingly Gatling (as in: the exception throw doesn't just fail the test).

Example:

<pre><code>// The scenario consists of a single test with two exec creating the execChain
val scn = scenario("MyAwesomeScenario").exec(reportableTest(

 // Send the request
 exec(http("127.0.0.1/Request").get(requestUrl).check(status.is(200)).check(bodyString.saveAs("MyData")

 // Process the data
 .exec(session =&gt; { 
 assert(processData(session.attributes("MyData")) == true, "Invalid data");
 })
))
</code></pre>

Above the scenario somewhere along the line "guardian failed, shutting down system".

Now this seems a useful, often-used thing to do - I'm possibly missing something simple. How to do it?

How to fail a Gatling test from within "exec"?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

带有一个执行链的Gatling场景。请求之后，将保存返回的数据。稍后，它将被处理，并且取决于处理结果，它要么失败，要么通过测试。这似乎是最简单的可能方案，但我找不到任何可靠的信息，如何在一个exec块内的测试失败。assert打破了场景，似乎是Gatling (如:异常抛出并不仅仅是测试失败)。示例：// The sc...

问如何从“主管”内部通过Gatling测试？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何从“主管”内部通过Gatling测试？EN