dgetzlaf commented on issue #6047: URL: https://github.com/apache/jmeter/issues/6047#issuecomment-1634284286
@vlsi thanks for your quick response! :) The `JSR223 Assertion` supports me a bit -> When a Sampler has a specific Assertion, I can add this Element for this Sampler. But since I long for a "more generic setup", the execution order of the given Assertions limits my use case. (JMeter adds the Assertions from "top to down".) By this I could concentrate on the Assertions, and avoid forget adding a second JSR223 Assertion. For example an use case, that appears sometimes on my test cases:  `1 - Login is OK` 1) `Persist Error` (as Assertion) is executed **No error is persisted (as wanted)** `2 - Login is NOK` 1) `Persist Error` (as Assertion) is executed **error is persisted (as wanted)** `3 - Login is http 200 with wrong response body` 1) `Persist Error` (as Assertion) is executed -> Nothing happens, since its http 200 1) `Response Assertion` is executed and fails **No error is persisted (as needed)** `4 - Login is http 200 with wrong response body` 1) `Persist Error` (as Assertion) is executed -> Nothing happens, since its http 200 1) `Response Assertion` is executed and fails 1) Additonal `Persist Error` (as Assertion) is executed **error is persisted (as wanted)** -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@jmeter.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
