You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Java 7 adds a new class javax.swing.JLayer, which we use for the root components of the tabs of a tabbed pane. When selecting the tab as the context in Robot we get an TestFailedException stating that the current context is not a "correct context".
Adding javax.swing.JLayer to the expected classes array in DefaultContextVerifier fixes the issue, but it creates a dependency on Java 7 from SwingLibrary.
The text was updated successfully, but these errors were encountered:
Damn... I think we should probably drop java 1.6 support at some point, but we cant drop that support yet. If you have an idea how to do this so that we still support 1.6, we could then fix this right away.
Though, I noticed that your tests use a mocking framework to create instances of the classes, and javax.swing.JLayer is a final class which cannot be mocked.
RF 2.9 is is going to require Jython 2.7 which in turn requires Java 7. Those who need to still use Java 6 (or 5) can obviously keep on using SwingLibrary with RF 2.8 or older, but perhaps they could also keep on using older SwingLibrary versions. Perhaps creating one more minor release with Java 6 support and then dropping it in the next major release would be a good plan.
Java 7 adds a new class
javax.swing.JLayer
, which we use for the root components of the tabs of a tabbed pane. When selecting the tab as the context in Robot we get anTestFailedException
stating that the current context is not a "correct context".Adding
javax.swing.JLayer
to the expected classes array inDefaultContextVerifier
fixes the issue, but it creates a dependency on Java 7 from SwingLibrary.The text was updated successfully, but these errors were encountered: