action #17898
closed[qam] test fails in firefox_java
50%
Description
Observation¶
openQA test in scenario sle-12-SP1-Desktop-DVD-Updates-x86_64-qam-regression-firefox@64bit fails in
firefox_java
Reproducible¶
Fails since (at least) Build 20170322-1
Expected result¶
Last good: 20170321-2 (or more recent)
Further details¶
Always latest result in this scenario: latest
Seems that we now need to accept certificate
Updated by pluskalm about 7 years ago
Oracles certificate states that it is valid till:
" Validity: [From: Thu Nov 13 01:00:00 CET 2014,
To: Mon Nov 13 00:59:59 CET 2017]"
Yet firefox claims it to be could not be verified - it however seems to be some sort of security enhancing behavior of firefox.
Updated by vsvecova about 7 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 50
Ah, I see the problem now. The security check part was already present in the test before, but it was occurring needlessly before the click on the "Verify Java version" button, when there was actually nothing to check for.
The error was not revealed before because the test used to pass in previous builds.
This was due to a bug in the IcedTea/Java OpenJDK plugin (bsc#982622), which was previously throwing an exception during the Verify Java version stage, therefore the test couldn't effectively proceed to the security check part and happily passed anyway.
(Example: https://openqa.suse.de/tests/827859#step/firefox_java/19)
An update fixing this bug has now been submitted, which revealed that the security check should occur after clicking the Verify Java version button.
Passing now on my OpenQA instance: http://dreamyhamster.suse.cz/tests/147#step/firefox_java/18
The pull request has been submitted: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/2601
Updated by coolo about 7 years ago
- Has duplicate action #17900: [qam] test fails in firefox_java added
Updated by coolo about 7 years ago
- Status changed from In Progress to Resolved
Your test run was lucky not to get the cookie popup. The problem is that the order of dialogs depends when the function is called, so coding the full workflow requires some more needle matches: https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/2605