5.0.0 - Java plugin not working

[krstcs]

Ranorex 5.0.0
Java 1.7

Java plugin no longer detects any objects inside the Java Security Warning dialog. The plugin can see the form, but not the buttons, text or checkbox elements.

On top of this, there is no longer a way to instrument the Java application, so I can't determine if that is the issue. I am aware of the changes, I read the change log for the new version. This was working in 4.1.5 and with 5.0.0 it isn't, and there wasn't anything in the change log about the Security Warning not working any longer.

The app I am testing is an internal application and the Security Warning needs to be automated during test runs, so this stops all testing of all of our system with 5.0.0. I cannot upgrade any systems to 5.0.0 as long as this problem exists. I understand the issues with Java security and internal applications in regards to certificates. We are working on that as well, but Ranorex should still work with the dialog, or there should have been something in the change log saying it was no longer supported.

[Support Team]

Hi,

I agree with you, it should work with 5.0 or should be stated that it no longer works.
I will check into this.

Meanwhile, may I ask you if Ranorex is able to identify other Java elements on your machine?
Do you just have problems with the specific Java security dialog?
Could you maybe also post a screenshot of the specific dialog?

Thanks,
Markus

[krstcs]

Yes, Ranorex identifies all other elements. This issue is only present for the Security Warning dialog.

The dialog is a Java form built into 1.7 and only appears when the JAR or JNLP file that you are running does not have a security manifest or correct digital signatures. (We are working to correct this issue in our application, but it isn't a high priority since the application is only used in-house.)

My guess is that this is due to the new way that Java is being instrumented.


Thanks Markus

[odklizec]

Here is another report about "something broken" in 5.0 Java plugin!

Please see the attached snapshots. Rx5.0 detects noticeably different path to SWT canvas and both Overview and Details lists show significantly less details about tracked SWT Canvas, than in 4.1.5.

LB3D_SWT_Canvas_RX5.0.rxsnp

LB3D_SWT_Canvas_RX4.1.5.rxsnp

Both snapshots were created with exactly the same AUT version and Java 1.7 (u11). The only difference is that the Rx5.0 snapshot has been created on Win7, while 4.1.5 was done on WinXP. But I don't think it's the cause of this problem?

[Support Team]

Hi,

Regarding the Security Warning dialog:
We unfortunately forgot to add this to the release notes. This dialog can no longer be tracked due to the changes in the Java instrumentation/plugin.
The problem is that the instrumentation gets loaded when the application is started, the dialog blocks the start up of the application and therefore the instrumentation/plugin isn't loaded.
A workaround would be using keyboard actions to select to run the app.

Regarding the snapshots:
This seems to be an issue on our site, we will analyze it and get back to you with more information.

Regards,
Markus

[krstcs]

Thanks Markus!

Yeah, I didn't even notice the keyboard shortcuts on the dialog until you said that. I'll try that and see what happens.

[krstcs]

OK, so after looking at the dialog again, it appears that the keyboard shortcuts are no longer there. Were they removed in the latest Java patch?

[Support Team]

Hi,

I am afraid I don't know which specific shortcuts you mean?
Beside that it should also work when you record images based actions.

Regards,
Markus

[krstcs]

In the screenshot I posted, the interactive elements (checkbox and buttons) all have direct keyboard shortcuts (notice the underlined letters). Those are no longer there.

But, I did figure out that the Cancel button is the default, so I can just send Tab key shortcuts and Space to select the elements.

So, thanks for the help!

[Support Team]

Hi,

I am glad you found a way to workaround this issue!

Regards,
Markus

[odklizec]

Hi,

I'm happy to report that our SWT Canvas problem is fixed in 5.0.1. Thanks!