GitHub user ham1 opened a pull request:
https://github.com/apache/jmeter/pull/355
BoundaryExtractor refactor
## Description
* Refactored `BoundaryExtractor`
* Ported tests to Spock
* Added more tests
* Other code tidyup while in the vicinity
## Motivation and Context
Took the need for a minor correction too far... but hopefully the code is
now slightly easier to understand.
## How Has This Been Tested?
unit tests and manual testing with Boundary Extractor GUI
## Screenshots (if appropriate):
## Types of changes
- Dev improvement
- Bug fix (non-breaking change which fixes an issue)
## Checklist:
<!--- Go over all the following points, and put an `x` in all the boxes
that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->
- [x] My code follows the [code style][style-guide] of this project.
- [x] I have updated the documentation accordingly.
[style-guide]: https://wiki.apache.org/jmeter/CodeStyleGuidelines
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/ham1/jmeter boundary_extractor_refactor
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/jmeter/pull/355.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #355
----
commit f1cd0042471ee698a0f9da266bdef5eb88181e15
Author: Graham Russell <[email protected]>
Date: 2017-12-10T21:43:02Z
BoundaryExtractor refactor
----
---
