HTTP parity regression#113
Open
3dgiordano wants to merge 40 commits into
Open
Conversation
# Conflicts: # pom.xml
…GRESSION # Conflicts: # src/test/java/com/blazemeter/jmeter/http2/sampler/JmxBlazeMeterHttpMigratorCliTest.java # src/test/java/com/blazemeter/jmeter/http2/sampler/JmxBlazeMeterHttpMigratorTest.java
…GRESSION # Conflicts: # pom.xml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces a comprehensive JMeter HTTP regression parity test suite, updates the build and CI configuration to support it, and improves code quality and consistency settings. The main themes are: adding regression testing infrastructure, updating Maven and CI configuration, and enforcing consistent code styles.
JMeter HTTP regression parity testing:
docs/jmeter-regression.mdguide describing the regression parity test suite, which compares the BlazeMeter HTTP sampler with JMeter's HttpClient4 across official test plans, and details how to run and interpret results.jmeter-regression,jmeter-regression-extended,jmeter-regression-external) inpom.xmlto enable tiered regression testing, with default test plan lists and properties for each group. [1] [2]ci-jmeter-compatibility.yaml) to run all regression test tiers and cache additional test resources.Build and dependency configuration:
ApacheJMeter_javaandcommons-io, and updated themaven-checkstyle-pluginversion and configuration. [1] [2] [3]maven-failsafe-pluginand Surefire plugin configuration to separate regression and non-regression integration tests and pass relevant system properties.Code style and repository consistency:
.gitattributesfile to enforce LF line endings on all text files for cross-platform consistency.checkstyle.xmlto move theLineLengthrule outside theTreeWalkermodule, ensuring consistent code style enforcement. [1] [2]These changes collectively improve the project's test coverage, CI reliability, and code quality.