Skip to content

Enable integration test for JetBrains IDEs #9203

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

Merged
merged 2 commits into from
Apr 13, 2022
Merged

Conversation

iQQBot
Copy link
Contributor

@iQQBot iQQBot commented Apr 8, 2022

Description

This PR introduces a very rudimentary version of the integration test for JetBrains IDEs
It uses the latest EAP version of Jetbrains Gateway, and test 4 IDEs at the same time (goland intellij phpstorm pycharm)

Related Issue(s)

Relate #7023

How to test

  1. start gitpod workspace in gitpod.io
  2. run command werft run github --remote-job-path=.werft/ide-integration-tests-startup-jetbrains.yaml github.com/gitpod-io/gitpod:pd/enable-jb-daily-job
  3. see the werft log and following integration test log

The important thing is the overall process of testing, not about test result

  1. create a new preview environment
  2. start 4 integration test job
  3. wait all test done
  4. wipe preview environment

Release Notes

NONE

Documentation

@iQQBot
Copy link
Contributor Author

iQQBot commented Apr 8, 2022

/hold
the test commit is required for review and test, but it SHOULD NOT merge

@akosyakov
Copy link
Member

 running test: /tests/jetbrains.test
 === RUN   TestJetBrainsGatewayWorkspace
 === RUN   TestJetBrainsGatewayWorkspace/Start_a_workspace_and_let_JetBrains_Gateway_connect
 === RUN   TestJetBrainsGatewayWorkspace/Start_a_workspace_and_let_JetBrains_Gateway_connect/it_can_start_a_workspace_and_let_JetBrains_Gateway_connect
     gateway_test.go:98: get or create user
     gateway_test.go:104: connecting to server...
     gateway_test.go:109: connected to server
     gateway_test.go:111: starting workspace
     gateway_test.go:114: cannot start workspace: "jsonrpc2: code 401 message: Unauthorized"
 --- FAIL: TestJetBrainsGatewayWorkspace (2.82s)
     --- FAIL: TestJetBrainsGatewayWorkspace/Start_a_workspace_and_let_JetBrains_Gateway_connect (2.82s)
         --- FAIL: TestJetBrainsGatewayWorkspace/Start_a_workspace_and_let_JetBrains_Gateway_connect/it_can_start_a_workspace_and_let_JetBrains_Gateway_connect (2.82s)
 FAIL
 Test failed at Mon Apr 11 07:07:52 UTC 2022
 Test suite ended with failure at Mon Apr 11 07:07:52 UTC 2022

expected?

akosyakov
akosyakov previously approved these changes Apr 11, 2022
Copy link
Member

@akosyakov akosyakov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It takes really a lot of time and one test failed, but it did work.

@iQQBot iQQBot force-pushed the pd/enable-jb-daily-job branch from 69b00c5 to fec51d8 Compare April 13, 2022 03:43
Copy link
Contributor

@mustard-mh mustard-mh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@iQQBot
Copy link
Contributor Author

iQQBot commented Apr 13, 2022

/unhold

@mustard-mh
Copy link
Contributor

mustard-mh commented Apr 13, 2022

/werft run no-preview

👍 started the job as gitpod-build-pd-enable-jb-daily-job.8

@roboquat roboquat merged commit 932556d into main Apr 13, 2022
@roboquat roboquat deleted the pd/enable-jb-daily-job branch April 13, 2022 05:32
@roboquat roboquat added deployed: IDE IDE change is running in production deployed Change is completely running in production labels Apr 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
deployed: IDE IDE change is running in production deployed Change is completely running in production release-note-none size/L team: IDE
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

4 participants