Skip to content

Commit

Permalink
Use correct message format for MessageFormat in HTMLAssertion
Browse files Browse the repository at this point in the history
Regression introduced by code clean up in commit af3958b

Bugzilla Id: 65782
  • Loading branch information
FSchumacher committed Jan 4, 2022
1 parent 51507ea commit 0083465
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 1 deletion.
Original file line number Diff line number Diff line change
Expand Up @@ -124,7 +124,7 @@ private AssertionResult runTidy(SampleResult inResponse) {
log.debug("Errors/warnings detected while parsing with tidy: {}", errbuf);
result.setFailure(true);
result.setFailureMessage(MessageFormat.format(
"Tidy Parser errors: {} (allowed {}) Tidy Parser warnings: {} (allowed {})",
"Tidy Parser errors: {0} (allowed {1}) Tidy Parser warnings: {2} (allowed {3})",
tidy.getParseErrors(), getErrorThreshold(), tidy.getParseWarnings(), getWarningThreshold()));
// return with an error

Expand Down
1 change: 1 addition & 0 deletions xdocs/changes.xml
Original file line number Diff line number Diff line change
Expand Up @@ -234,6 +234,7 @@ however, the profile can't be updated while the test is running.
<li><bug>65352</bug>Warning logged when Boundary Extractor doesn't find any match</li>
<li><bug>65681</bug>Use default values for null values when extracting with JSONPostProcessor</li>
<li>Allow setters in ConstantThroughputTimer to updating the values during the run time</li>
<li><bug>65782</bug>Use correct message format for MessageFormat in HTMLAssertion</li>
</ul>

<h3>Functions</h3>
Expand Down

0 comments on commit 0083465

Please sign in to comment.