jgaalen commented on issue #3364: URL: https://github.com/apache/jmeter/issues/3364#issuecomment-1466525124
> Extractors are not the place to fail a sampler. Their job is strictly to extract. Assertions are the correct place for failing a sampler. Please re-close this ticket. > […](#) > On Fri, Mar 10, 2023, 10:49 jgaalen ***@***.***> wrote: I'd like to reopen this ticket. It is a great addition. By far in most cases you want the sampler to fail if the regex extraction fails. Adding a response assertion with the exact same match is very unproductive, mostly forgotten and consumes extra resources. The argument that the response assertion can already do that is irrelevant in my opinion. There are tons of features that can be done by other options. this feature would be a valuable addition to jmeter without compromising anything — Reply to this email directly, view it on GitHub <[#3364 (comment)](https://github.com/apache/jmeter/issues/3364#issuecomment-1463468682)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAXQDSUNX6FBJRPIELKAIQ3W3LTI7ANCNFSM6AAAAAAVWEQNUE> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***> It might be a bit of a semantic discussion, but it's actually under 'Post Processor', and extracting + failing a request is exactly what a post processor can do. If a check box with 'Fail if not found' is too much for the extractors, perhaps create a similar post processor which does this: extract and fail if nog found. I think this is an important feature for a performance test tool (all other tools simply support this tho). I have seen tons of scripts made by others and I have never seen people duplicating their extractions to an assertion to make sure it actually extracted a value. If you don't do that, you have the risk that you just continue in the script and send bogus data and let the script fail too late. For the matter of creating sensible scripts, this feature is a must have in my opinion. On the other hand, some scripts can have very cpu heavy extractors (regex/xml) and you don't want to duplicate them just to make there there's a value, especially when you extract 5+ values. It will drain the cpu because it will do double the work -- 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
