Match No differs in Boundary & RegExp Post-Processors
Open
defect
to-triage
- Dominant language
- Java
- Stars
- 9.5k
- Forks
- 2.3k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 5
Description
### 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]
Contributor guide
Assessment
This issue has not been assessed yet.