Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpectedly absent the warning marker in the editor #7161

Closed
artaleks9 opened this issue Nov 2, 2017 · 6 comments
Closed

Unexpectedly absent the warning marker in the editor #7161

artaleks9 opened this issue Nov 2, 2017 · 6 comments
Assignees
Labels
e2e-test/failure Issues that is related to a test failures reported by our CI platform and our QE. kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the usage or development of the system. sprint/current

Comments

@artaleks9
Copy link
Contributor

artaleks9 commented Nov 2, 2017

  • Sometimes selenium tests from 'opendeclaration' package are failed by reason not present warning markers
  • Another case of failing test: after perform the 'open declaration' (F4) the expected file is absent in the editor
  • As a rule it happen when tests were running on CI, but on local host the tests are passed
  • We need to fix up it
  • Related selenium tests: Eclipse0093Test, Eclipse0115Test, Eclipse0121Test , AutocompleteProposalJavaDocTest , AutocompleteWithInheritTest , ShowHintsCommandTest
@artaleks9 artaleks9 added kind/task Internal things, technical debt, and to-do tasks to be performed. status/in-progress This issue has been taken by an engineer and is under active development. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Nov 2, 2017
@artaleks9 artaleks9 self-assigned this Nov 2, 2017
@artaleks9 artaleks9 removed the status/in-progress This issue has been taken by an engineer and is under active development. label Nov 7, 2017
@artaleks9
Copy link
Contributor Author

After merging the pull request #7164 the problem is not reproduced on CI

@vkuznyetsov vkuznyetsov added team/production and removed status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Nov 7, 2017
@dmytro-ndp
Copy link
Contributor

dmytro-ndp commented Dec 13, 2017

We have the same test failure again on CI https://ci.codenvycorp.com/view/qa/job/che-integration-tests-che6/113/testReport/junit/org.eclipse.che.selenium.opendeclaration/Eclipse0115Test/test0115/:

org.openqa.selenium.TimeoutException: Expected condition failed: waiting for visibility of element located by By.xpath: //div[@class='ruler overview']/div[@class='annotationOverview warning'] (tried for 20 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.0.1', revision: '1969d75', time: '2016-10-18 09:49:13 -0700'
System info: host: 'slave6.codenvycorp.com', ip: '127.0.0.1', os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-514.16.1.el7.x86_64', java.version: '1.8.0_102'
Driver info: org.eclipse.che.selenium.core.SeleniumWebDriver
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:80)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:265)
	at org.eclipse.che.selenium.pageobject.CodenvyEditor.waitMarkerInPosition(CodenvyEditor.java:627)

org eclipse che selenium opendeclaration eclipse0115test test0115_qqldkvfe

@dmytro-ndp dmytro-ndp reopened this Dec 13, 2017
@dmytro-ndp
Copy link
Contributor

Another unstable test: org.eclipse.che.selenium.opendeclaration.Eclipse0121Test.test0121():

  org.openqa.selenium.TimeoutException: Expected condition failed: waiting for visibility of all elements located by By.xpath: //div[@id='gwt-debug-multiSplitPanel-tabsPanel']//div[text()='Collections'] (tried for 10 second(s) with 500 MILLISECONDS interval)
Build info: version: '3.0.1', revision: '1969d75', time: '2016-10-18 09:49:13 -0700'
System info: host: 'slave6.codenvycorp.com', ip: '127.0.0.1', os.name: 'Linux', os.arch: 'amd64', os.version: '3.10.0-514.16.1.el7.x86_64', java.version: '1.8.0_102'
Driver info: org.eclipse.che.selenium.core.SeleniumWebDriver
	at org.openqa.selenium.support.ui.WebDriverWait.timeoutException(WebDriverWait.java:80)
	at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:265)
	at org.eclipse.che.selenium.pageobject.CodenvyEditor.waitTabIsPresent(CodenvyEditor.java:1114)
	at org.eclipse.che.selenium.opendeclaration.Eclipse0121Test.test0121(Eclipse0121Test.java:60)

org eclipse che selenium opendeclaration eclipse0121test test0121_61hlm96w

@vkuznyetsov vkuznyetsov added the status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. label Dec 19, 2017
@artaleks9
Copy link
Contributor Author

Right now the problem is not reproduced on CI

@artaleks9
Copy link
Contributor Author

artaleks9 commented Jan 15, 2018

The problem is again actual, so the issue is reopened and delegate to developer team

@artaleks9 artaleks9 reopened this Jan 15, 2018
@artaleks9 artaleks9 removed their assignment Jan 15, 2018
@artaleks9 artaleks9 added kind/bug Outline of a bug - must adhere to the bug report template. e2e-test/failure Issues that is related to a test failures reported by our CI platform and our QE. severity/P2 Has a minor but important impact to the usage or development of the system. team/ide and removed kind/task Internal things, technical debt, and to-do tasks to be performed. team/production sprint/current status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. labels Jan 15, 2018
@artaleks9 artaleks9 changed the title Stabilize selenium tests from 'opendeclaration' package Unexpectedly absent the warning marker in the editor Jan 15, 2018
Ohrimenko1988 added a commit that referenced this issue Feb 15, 2018
…tests related with bug "#7161" for increase stability (#8797)
@artaleks9
Copy link
Contributor Author

The working of product is OK from developer side
And it resolved by the #8797

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
e2e-test/failure Issues that is related to a test failures reported by our CI platform and our QE. kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the usage or development of the system. sprint/current
Projects
None yet
Development

No branches or pull requests

5 participants