ashrafiucse commented on PR #6758: URL: https://github.com/apache/jmeter/pull/6758#issuecomment-5463499900
Hi @vlsi — I saw your compatibility concern on #6753 and want to address it here before this PR goes the same way. This PR reads both names (load-time migration in `setProperty`, so plans saved with `Asserion.test_strings` keep working), and unlike #6753 the schematic XSL matches **both** names so old plans still render. However I understand the remaining gap: files saved by this JMeter carry the new name only, so tools that hard-code the misspelled name when *reading* JMX (e.g. the MeterSphere extension you linked) would lose the patterns. If the project prefers your middle ground — JMeter responding to two property names at the same time — I'm happy to rework this to also keep writing the legacy `Asserion.test_strings` collection alongside the correctly spelled one (kept in sync on every mutation), so old and new plugins/tools keep working. Just let me know which direction you'd like. (Also noting #6751 is a duplicate of #6289 — this PR tracks #6289.) -- 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]
