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

Add fail option for regex extractor #6256

Open
wants to merge 5 commits into
base: master
Choose a base branch
from

Conversation

jgaalen
Copy link

@jgaalen jgaalen commented Mar 22, 2024

Description

This change adds the option to automatically fail a sampler if a regular expression extraction can't find any matches.

Motivation and Context

This saves the need to add an assertion with a regex to be sure there are matches. This will either save doing the regex matching twice and/or improved the scripts by failing if the extraction fails rather fail later when there is no value

Based on this discussion. Thanks to @asfimport for initiating this and providing code

How Has This Been Tested?

I've tested this on HTTP Requests only with different types of matches (1: single extraction, 0: random and -1 to match multiple fields)

Screenshots (if appropriate):

Types of changes

  • New feature (non-breaking change which adds functionality)

Checklist:

  • My code follows the code style of this project.
  • I have updated the documentation accordingly.

@@ -208,6 +214,8 @@ private JPanel makeParameterPanel() {
templateField = new JLabeledTextField(JMeterUtils.getResString("template_field")); //$NON-NLS-1$
refNameField = new JLabeledTextField(JMeterUtils.getResString("ref_name_field")); //$NON-NLS-1$
matchNumberField = new JLabeledTextField(JMeterUtils.getResString("match_num_field")); //$NON-NLS-1$
failResultField = new JLabel(JMeterUtils.getResString("fail_if_not_matched_field"));
failResult = new JCheckBox();
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you use JEditableCheckBox here?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

emptyDefaultValue is also a JCheckBox(), so what would a JEditableCheckbox do better?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm using JLabel + JCheckBox here because it's nicer to have the label in the same row as the others and the checkbox in the column of the input fields

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

JEditableCheckbox would allow using ${..} expressions while JCheckBox, see #5944

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, although the JEditableCheckbox is a nice feature to paramaterize scripts, I don't think it's a good usecase on this specific checkbox. I don't see a reason to parameterize a specific regex extractor. The other checkboxes on the Regex Extractor aren't an editable checkbox as well.
I can give it a try tho, If it doesn't help, it doesn't hurt

Copy link
Collaborator

@vlsi vlsi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Have you considered adding test case for the feature?

@@ -41,7 +41,7 @@
* {@code @Isolated}.
*/
@Isolated
public abstract class JMeterTestCase {
public abstract class JMeterTestCase {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please refrain from making changes that are not a part of the PR

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, somehow it was updated by a plugin I guess and didn't bothered fixing it. Will undo this

@@ -57,7 +58,7 @@ public class RegexExtractor extends AbstractScopedTestElement implements PostPro
* These are passed to the setUseField() method
*
* Do not change these values!
*/
*/
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please refrain from making changes that are not a part of the PR

Comment on lines 259 to 260
log.debug("Input = '{}'", inputString);
return inputString;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please refrain from making changes that are not a part of the PR

@@ -472,7 +484,7 @@ private void initTemplate() {
PatternMatcher matcher = JMeterUtils.getMatcher();
Pattern templatePattern = JMeterUtils.getPatternCache().getPattern("\\$(\\d+)\\$" // $NON-NLS-1$
, Perl5Compiler.READ_ONLY_MASK
| Perl5Compiler.SINGLELINE_MASK);
| Perl5Compiler.SINGLELINE_MASK);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please refrain from making changes that are not a part of the PR

@@ -382,6 +382,7 @@ public void GUIComponents2(GuiComponentHolder componentHolder) throws Exception
IGNORED_PROPERTIES.add(LoopControllerSchema.INSTANCE.getContinueForever());
IGNORED_PROPERTIES.add(RegexExtractorSchema.INSTANCE.getMatchTarget());
IGNORED_PROPERTIES.add(RegexExtractorSchema.INSTANCE.getDefaultIsEmpty());
IGNORED_PROPERTIES.add(RegexExtractorSchema.INSTANCE.getFailIfNotFound());
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you clarify why adding the property here? Ideally the list of "ignored properties" should be empty. I should add a clarification javadoc to IGNORED_PROPERTIES so it clarifies its purpose.

Copy link
Author

@jgaalen jgaalen Mar 25, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have no idea, if I don't add this line the build fails on the tests:

 org.opentest4j.AssertionFailedError: GUI element class org.apache.jmeter.extractor.gui.RegexExtractorGui org.apache.jmeter.extractor.gui.RegexExtractorGui[${test_TestElement.name},0,0,0x0,invalid,layout=java.awt.BorderLayout,alignmentX=0.0,alignmentY=0.0,border=javax.swing.border.EmptyBorder@10142fa,flags=9,maximumSize=,minimumSize=,preferredSize=] be able to pass all the properties to a different TestElement ==> expected: <org.apache.jmeter.extractor.RegexExtractor::class {
        props {
            it[name] = "\${test_TestElement.name}"
            it[guiClass] = "org.apache.jmeter.extractor.gui.RegexExtractorGui"
            it[referenceName] = "\${test_RegexExtractor.refname}"
            it[regularExpression] = "\${test_RegexExtractor.regex}"
            it[template] = "\${test_RegexExtractor.template}"
            it[default] = "\${test_RegexExtractor.default}"
            it[matchNumber] = "\${test_RegexExtractor.match_number}"
            it[failIfNotFound] = "\${test_RegexExtractor.fail_if_not_found}"
            it[comments] = "\${test_TestPlan.comments}"
        }
    }
    > but was: <org.apache.jmeter.extractor.RegexExtractor::class {
        props {
            it[name] = "\${test_TestElement.name}"
            it[guiClass] = "org.apache.jmeter.extractor.gui.RegexExtractorGui"
            it[comments] = "\${test_TestPlan.comments}"
            it[referenceName] = "\${test_RegexExtractor.refname}"
            it[regularExpression] = "\${test_RegexExtractor.regex}"
            it[template] = "\${test_RegexExtractor.template}"
            it[default] = "\${test_RegexExtractor.default}"
            it[matchNumber] = "\${test_RegexExtractor.match_number}"
            it[failIfNotFound] = false
        }
    }

previousResult.setSuccessful(false);
AssertionResult res = new AssertionResult(getName());
res.setFailure(true);
res.setFailureMessage("Pattern not found: " + getRegex());
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest including the "source" that was checked against the regexp. In other words, something like `Pattern ... not found in ...<response body | ... >"

@jgaalen
Copy link
Author

jgaalen commented Mar 25, 2024

Have you considered adding test case for the feature?

Not really, I'm not really into this. I've tried to make something out of an earlier existing (working) code for this feature as you've asked me to create a PR and would love this feature in JMeter, but I'm not a java developer. Can you help me out?

@jgaalen
Copy link
Author

jgaalen commented Nov 8, 2024

Have you considered adding test case for the feature?

I've added unit tests and fixed some of your items. Seems to be working out really well

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

Successfully merging this pull request may close these issues.

2 participants