Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Match No differs in Boundary & RegExp Post-Processors #6378

Open
d1ckb31n opened this issue Nov 4, 2024 · 0 comments
Open

Match No differs in Boundary & RegExp Post-Processors #6378

d1ckb31n opened this issue Nov 4, 2024 · 0 comments

Comments

@d1ckb31n
Copy link

d1ckb31n commented Nov 4, 2024

Expected behavior

Match should be 1 if field Match No. is not set (empty). Documentation lacks an entry for empty field at all. Only 0 and nth match is described.

Actual behavior

RegExp Extractor uses the first match whereas Boundary Extractor uses a random match in case the match no is empty.
Both should behave identical/consistent.

Steps to reproduce the problem

Add a regexp extractor and a boundary extractor to the testplan. Extract the same value using both post-processors. Display the result via Debug pre-processor

JMeter Version

5.6.3

Java Version

openjdk version "21.0.2" 2024-01-16 LTS

OS Version

Microsoft Windows [Version 10.0.19045.5011]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant