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

Investigate reasons of randomly not parsed java files in the selenium tests #8527

Closed
Ohrimenko1988 opened this issue Jan 31, 2018 · 1 comment
Assignees
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed.

Comments

@Ohrimenko1988
Copy link
Contributor

Ohrimenko1988 commented Jan 31, 2018

Sometimes java files are not parsed. That's why we have randomly fails of the selenium tests which related to displaying warning marker and autocomplete. We need to investigate this problem and collect information as much as we can.

Report with reproduced problem:
https://ci.codenvycorp.com/view/qa/job/che-integration-tests-master-docker/165/Selenium_tests_report/

Screenshot:

rrrr

@Ohrimenko1988
Copy link
Contributor Author

Ohrimenko1988 commented Mar 5, 2018

The problem was in use "ProjectExplorer#quickExpandWithJavaSkript()" method which expands project explorer tree by using "JavaSkript". It does not emulate the clicks on each node and some events may be not launched. This may be very critical for use cases where test waits for some event already after quick expand. So in this cases, we have to use "ProjectExplorer#expandPathInProjectExplorer(String path)" method, which emulates the native clicks.

@Ohrimenko1988 Ohrimenko1988 removed the status/in-progress This issue has been taken by an engineer and is under active development. label Mar 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Internal things, technical debt, and to-do tasks to be performed.
Projects
None yet
Development

No branches or pull requests

2 participants