Skip to content

Releases: Blazemeter/RTEPlugin

v3.3

13 Mar 17:51
6fd6a80
Compare
Choose a tag to compare

This release includes the following changes:

  • Changed the behavior of the VT protocol to avoid waiting for server response in each character sent.
  • Fixed an issue in VT protocol when trying to send special characters with Shift + key combination.

3.2.2

26 Oct 17:14
0691b0f
Compare
Choose a tag to compare

What's new on this patch release

Bug fixing:

  • Update dm3270 dependency to v0.15, which allows the error-free execution of commands not supported by the emulated terminal.

3.2.1

25 Nov 20:35
Compare
Choose a tag to compare

What's new on this patch release

  • Add support for TN3270 circular fields
  • Add support for alarm in VT220

Bug fixing:

  • Fix alignment of emulator screen when using high resolutions
  • Fix APL charset use cases
  • Many more

3.2

09 Jun 13:11
65a950f
Compare
Choose a tag to compare
3.2

What's new on this minor release

  • Wait for disconnect support.
    • Now is possible to assert when a server disconnection occurs.

    E.g: Makes possible to validate the behave of a LOGOFF command.

  • Automatic Wait for Disconnect recognition.
    • When using the Recorder the Terminal Emulator will automatically detect for a server disconnection. Therefore a Wait for Disconnect is recorded and added to the current sampler.
  • We have also fixed some issues:
    • Frozen screen when recording TN3270 protocol.
    • Not possible to send spaces as input.

3.1.1

18 Feb 17:42
e71603c
Compare
Choose a tag to compare

This patch release includes the following changes:

  • Fixed issue on InputByTab when recording
  • Fixed screen to support a large range of screens
  • Added support for ALP charset
  • Consecutive input by label support

3.1

18 Aug 16:59
Compare
Choose a tag to compare
3.1

What's new on this minor release:

  1. Fix issue when sending Attention Key on screens not constituted by fields. (TN5250 protocol)
  2. Add support for sending an attention key at a determined position. This feature is very useful for scenarios where screens aren't constituted by fields, and there is a menu waiting for an ENTER key to be pressed on the desired position.

    In order to set the cursor position when building manually the TestPlan, would be adding a Position Input with the coordinates where we want to place the cursor, and then, is mandatory to set the value of the input, empty. The Recorder will do this automatically. For more information click here

  3. Fix issue when the sample name kept changing when sending inputs using VT420 protocol alongside with the Recorder.

3.0.1

11 Jun 02:08
ca03189
Compare
Choose a tag to compare

In this patch release, we fixed an issue that was causing no emulator interaction after setting the sample name while recording a VT protocol.

3.0

19 May 22:23
Compare
Choose a tag to compare
3.0

In this third major release, we have added support for the VT-420 protocol!
For further information check the documentation.
Supported functionalities for this protocol:

  • Input by Navigation
  • Wait conditions:
    • Wait for text
    • Wait for silent
    • Wait for cursor
  • Attention keys
  • Test plan recording support:
    • Create your test plan just by interacting with an emulator!

WARNING: Input by Position and Input by Label are not supported in this release.

What's new:

  • Input by Navigation
    • This new input is adding the possibility to navigate through the screen via a sampler. This input consists of a navigation type which could be: up, down, left, right arrows or even a tabulator

      Navigation input is also supported for tn3270 and tn5250 protocols.

  • Recorder default input:
    • Previously when using the recorder and no Input by Label was specified, an input by position was created on the sampler. This behavior has been changed, now an input by navigation is added as default recorder input

      This change was done in order to prioritize the test plan maintainability and its robustness. As an example, if you have recorded a flow using a Coordinates Input, and for some reason, the screen moves a little bit the field position, then the test will fail. But if you use a Navigation Input and more precisely a tabulator one, even if the position of the fields has changed, you would still run the test without any issue.

2.3

19 Feb 20:26
4572601
Compare
Choose a tag to compare
2.3

This release comes with a new feature for the plugin, check the documentation for more information.

What's new:

  • Tabulator input support.
    • Now you can create a new type of input called Tabulator Input, which will allow you instead of defining the coordinates, as usual, to send a value with differents amount of tabs before the input.

2.2.1

15 Jan 16:43
3456181
Compare
Choose a tag to compare
  • In this patch version we have fixed wait conditions.
    • Wait for text condition has change a little bit it's behaviour. Now it is more focused on the condition, if we are matching a text in the screen but suddenly the screen changes, but the chunk of text to match still is in the screen, then the condition meets anyway.
    • Wait for cursor has been modified in order to be more robust.
  • Documentation updated.
  • Issue related to empty field in the Post Processor RTE-Extractor fixed!