ensure not throwing error
See original GitHub issueSetting I have a very basic configuration file with 3 ensure checks.
config:
target: <omitted-target>
phases:
- duration: 20
arrivalRate: 5
rampTo: 10
name: Sustained load
ensure:
p95: 100
max: 200
maxErrorRate: 1
scenarios:
- name: "Visit Landing"
flow:
- get:
url: "/"
I run artillery/2.0.0-10 win32-x64 node-v14.15.3
.
What’s going wrong? Running this test I get the following report summary.
--------------------------------
Summary report @ 12:48:14(+0100)
--------------------------------
vusers.created_by_name.Visit Landing: .......................................... 148
vusers.created.total: .......................................................... 148
vusers.completed: .............................................................. 148
vusers.session_length:
min: ......................................................................... 197.4
max: ......................................................................... 422.1
median: ...................................................................... 247.2
p95: ......................................................................... 320.6
p99: ......................................................................... 347.3
http.request_rate: ............................................................. 8/sec
http.requests: ................................................................. 148
http.codes.200: ................................................................ 148
http.responses: ................................................................ 148
http.response_time:
min: ......................................................................... 101
max: ......................................................................... 274
median: ...................................................................... 138.4
p95: ......................................................................... 194.4
p99: ......................................................................... 242.3
Log file: test.json
As you can see the ensure condition p95 = 194.4 > 100 = ensure.p95
is violated. Unfortunately, there is no error thrown stating that the respective ensure condition has failed.
What’s expected?
I would expect to get an error like ensure condition failed: ensure.p95 < 100
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (2 by maintainers)
Top Results From Across the Web
How to test that no exception is thrown? - java - Stack Overflow
The first unit of work should test whether or not a valid user is being returned in the case of valid and invalid...
Read more >How to test a function that's expected to throw error in jest…
Say, I want to write a test for the function below and want to ensure I test if it actually fails when the...
Read more >Best Practices for exceptions - .NET - Microsoft Learn
Learn best practices for exceptions, such as using try/catch/finally, handling common conditions without exceptions, and using predefined .
Read more >10 Handling PL/SQL Errors
Exceptions cannot propagate across remote procedure calls done through database links. A PL/SQL block cannot catch an exception raised by a remote subprogram....
Read more >Error handling and automatic retries in AWS Lambda
Function – Your function's code throws an exception or returns an error object. ... If you retry, ensure that your function's code can...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@jclusso oops, a case of documentation being updated before a new release and going out of sync 🤦♂️ Could you try again with the latest version of
artillery
andartillery-plugin-ensure
please?Example script to try with:
Sorry for the late response. I can confirm that the issue is resolved with @hassy’s response. Thank you!