Blazemeter / RTEPlugin

JMeter RTE (TN5250, TN3270 & VT420) plugin for testing Mainframe applications
Apache License 2.0
19 stars 11 forks source link

IBM TN3270 #23

Open amit1986kumar opened 2 years ago

amit1986kumar commented 2 years ago

Hi, I am able to connect mainframe with RTE plugin and able to navigate to login page. Here user id field is showing non editable in mainframe CICS screen, but password field is working fine. Now not sure why it is non editable, I cross checked in IBM tn3270 there it is working fine. Can you please advice what I need to do to fix this for testing.

Baraujo25 commented 2 years ago

Hi @amit1986kumar, thanks for reaching out!

We are about to release a version that might cover the issue you're facing. However, if you could provide a TCP dump of the flow you're trying to record, that would be very helpful for us in order to identify, debug and fix your issue.

In order to get the TCP dump, you can review this instructions, it's possible to be obtained by using an Open Source terminal emulator or even using Wireshark to get the tcp traffic.

If you encounter any issue just let us know!

Bests,

Joaquin

amit1986kumar commented 2 years ago

I have observed that my application have used "under lines" to input the data. But RTE tool is accepting only non underlines as input area, where underlines are used to enter the data line in USER ID case, it is marking those as un-editable area. I am attaching the log for the reference. Also I feel this need to be able to edit or replace the values in editable fields, where underlines used or not.

Kindly keep this confidential.

Baraujo25 commented 2 years ago

Already reviewed 👍 You can reach me out to joaquin.araujo@blazemeter.com as specified in my profile. In order to keep the confidentiality.

I'll be looking forward to hear from you.

Baraujo25 commented 2 years ago

The JMeter log file you provide is not enough to detect what the actual issue is. Without a TCP dump it's not going to be possible to fix this behaviour.

Context

Once we get the TCP dump, we parse the telnet connection in order to replicate the flow you are trying to do but locally.

We inject the dump in an Open Source project called Wiresham which allows us to run the same scenario as the one you are trying to record. Wiresham is just a simple mocking tool.

In that way, we don't need to actually get access to your mainframe application to debug and fix. The TCP dump is usually enough.

Please check this documentation in order to get the TCP dump. You'll find two alternatives in order to get the dump, I'll recommend you this one which is faster and easy.

Additionally, consider sending the dump via email (joaquin.araujo@blazemeter.com) in order to maintain confidentiality.

I'll be looking forward to hear from you.

amit1986kumar commented 2 years ago

Hi Team,

I have captured the log and converted the same to Json format. Kindly review and download. I will remove this post, after your review.

I am looking forward to have a fix for this issue.

Baraujo25 commented 2 years ago

Hey, thanks for the dump.

I'll let you know when the issue is addressed.

In the meantime I will recommend you to keep sync since we expect a release during this week that might fix your issue.