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

Fix Java selenium E2E tests which check integration with GitHub #14711

Closed
3 of 20 tasks
dmytro-ndp opened this issue Sep 30, 2019 · 1 comment
Closed
3 of 20 tasks

Fix Java selenium E2E tests which check integration with GitHub #14711

dmytro-ndp opened this issue Sep 30, 2019 · 1 comment
Assignees
Labels
e2e-test/failure Issues that is related to a test failures reported by our CI platform and our QE. severity/P1 Has a major impact to usage or development of the system.

Comments

@dmytro-ndp
Copy link
Contributor

dmytro-ndp commented Sep 30, 2019

There are two Java selenium tests constantly failing :

  • ImportProjectFromGitHubTest
  • AuthorizeOnGithubFromDashboardTest

For example: https://ci.codenvycorp.com/view/pr-builds/job/che-pullrequests-test-ocp/2461/Selenium_20tests_20report/

Runtime

  • kubernetes (include output of kubectl version)
  • Openshift (include output of oc version)
  • minikube (include output of minikube version and kubectl version)
  • minishift (include output of minishift version and oc version)
  • docker-desktop + K8S (include output of docker version and kubectl version)
  • other: (please specify)

Installation method

  • chectl
  • che-operator
  • minishift-addon
  • ocp.sh script

Environment

  • my computer
    • Windows
    • Linux
    • macOS
  • Cloud
    • Amazon
    • Azure
    • GCE
    • other (please specify)
  • other: Codenvy CI

Related issue

#7899

@dmytro-ndp dmytro-ndp added e2e-test/failure Issues that is related to a test failures reported by our CI platform and our QE. team/che-qe labels Sep 30, 2019
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 30, 2019
@dmytro-ndp dmytro-ndp added severity/P1 Has a major impact to usage or development of the system. sprint/current and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Sep 30, 2019
@artaleks9 artaleks9 added the status/in-progress This issue has been taken by an engineer and is under active development. label Sep 30, 2019
@artaleks9 artaleks9 removed the status/in-progress This issue has been taken by an engineer and is under active development. label Oct 3, 2019
@artaleks9
Copy link
Contributor

It was created new GitHub test account and registered needed OAuth applications. New Client/Secret IDs were added to the qa-slaves on the https://ci.codenvycorp.com/view/qa-nightly/.
Now it works as expected.

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. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Development

No branches or pull requests

4 participants