-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Decouple Java selenium E2E tests from GWT-code #13827
Comments
How much work is required by "rewrite Dashboard tests which use GWT-editor to check changes in Dashboard."? It's more than half a day can we postpone it after GA? |
I was thinking in this issue just in scope of Che 7 release - basically making the code "compilable" (that's why the che7GA target). I don't care much about the old tests and if something can be saved from existing tests with minimal amount of work, it should be done as part of different issue. I'll edit the description of this one and create another one for possible followup work. |
Thinking again about this... For Che7GA, disabling whole |
@rhopp: if we disable Java selenium e2e tests, we will stop testing IDE Dashboard on regular basis. |
We can clean up and enable Java selenium tests, but disable particular tests which we are going to re-write (step 1, 2 from description). It's about several days of work, IMHO. |
Right now I'm most interested in amount of test-cases which would work without any refactoring (after the build-time dependencies are removed). |
Description
There is a plan to remove GWT-related code from Che #13788, and Java E2E selenium tests should be aligned with this changes:
The text was updated successfully, but these errors were encountered: