waterWang opened a new pull request, #6753: URL: https://github.com/apache/jmeter/pull/6753
## Description Fixes the misspelled property name `Asserion.test_strings` (missing the letter 't') used by the Response Assertion component. Every other property in `ResponseAssertion` uses the `Assertion.` prefix; the typo causes inconsistency and leaks the misspelled name into saved `.jmx` test plans and the schematic XSL output. Closes #6751 ## Changes 1. **`ResponseAssertion.java`** — the `TEST_STRINGS` constant now uses the correctly spelled `Assertion.test_strings` name, and a legacy constant keeps the old misspelled value. 2. **Backward compatibility** — `getTestStrings()` migrates an existing test plan's legacy `Asserion.test_strings` property to the correctly spelled name on read, so no stored assertion configuration is lost and newly saved plans use the correct name. 3. **`schematic.xsl`** — the XSL now selects the correctly spelled `Assertion.test_strings` property for the assertion schematic. ## How Has This Been Tested? - The migration path mirrors the existing `NullProperty` handling already used in this class. - Existing `ResponseAssertionTest` unit tests exercise the getter/setter flows (add/clear test strings), which are unaffected. - The numerous `.jmx` files under `bin/testfiles/` intentionally keep the legacy name — they serve as regression fixtures proving old plans still load and migrate. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
