2.1
This releases adds following new features to the RTE test plan recorder, check the associated changes in README:
- Ability to select an area of the screen and use it as wait condition to mark the end of the previous interaction (use it as wait for text on recorded sampler).
- This allows for more robust conditions to detect when next interaction (sampler) should be triggered, specifying a particular text on the screen marking the completion of the processing from mainframe application. Even through default recorded wait conditions are good in most of the cases, we encourage RTE test plan recorder users to use this feature to have more robust test plans.
- Allow to select an area of the screen to be used as input label for more robust auto completion of input fields.
- By recording test plans with inputs by label (instead of the default behavior which uses fields positions) your test plans will not be affected by changes in positions of fields in the screen (in particular when screens may vary from user to user).
- Allow to record assertions for recorded samplers by selecting a screen area.
- We encourage users to use wait for text recording functionality instead of assertions whenever possible, since they are more robust than using assertions (i.e.: wait for text waits for the text to appear and if not it timeouts, assertions just fail and the update of the screen might have not yet happened). But in some cases it might be helpful to specify a text for wait for text, and define different assertions for other parts of the screen.
Additionally, it includes the changes on dm3270 lib 0.11 release that fix handling input by label on screens generated for SSCP LU session.
Finally, sample results generated by plugin have been simplified and made compatible with older versions of the plugin avoiding forward compatibility issue while loading JTL files in JMeter introduced by 2.0 release.