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.

Sign up for GitHub

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

Jump to bottom

[code] integration test cut-through #3065

Closed
4 of 6 tasks
akosyakov opened this issue Feb 1, 2021 · 14 comments
Closed
4 of 6 tasks

[code] integration test cut-through #3065

akosyakov opened this issue Feb 1, 2021 · 14 comments
Assignees
@jeanp413
Labels
aspect: testing Anything related to testing Gitpod manually, automated integration tests or even unit tests editor: code (browser) meta: never-stale This issue can never become stale team: IDE

Comments

@akosyakov
Copy link
Member

akosyakov commented Feb 1, 2021 •
edited
Loading

It would be good to automate testing of Code integration.

Tasks
@csweichel
Copy link
Contributor

Ideally integrated into our integration tests, so that the Code integration tests would be part of Gitpod's integration tests.

@csweichel csweichel added the aspect: testing Anything related to testing Gitpod manually, automated integration tests or even unit tests label Feb 2, 2021
@stale
Copy link

stale bot commented Mar 16, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Mar 16, 2021
@akosyakov akosyakov removed the meta: stale This issue/PR is stale and will be closed soon label Mar 17, 2021
@stale
Copy link

stale bot commented Jun 15, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Jun 15, 2021
@stale stale bot closed this as completed Jun 25, 2021
@akosyakov akosyakov reopened this Jun 26, 2021
@stale stale bot removed the meta: stale This issue/PR is stale and will be closed soon label Jun 26, 2021
@akosyakov akosyakov added meta: never-stale This issue can never become stale meta: stale This issue/PR is stale and will be closed soon labels Jun 26, 2021
@stale stale bot removed the meta: stale This issue/PR is stale and will be closed soon label Jun 26, 2021
@akosyakov
Copy link
Member Author

We do really a lot of repetitive testing each month. It is better to look into how it can be automated.

@akosyakov
Copy link
Member Author

There are some smoke tests in VS Code repo: https://github.com/Microsoft/vscode/blob/main/test/smoke/README.md Maybe we can do something based on them.

@akosyakov akosyakov added the priority: high (dev loop impact) Gitpod development loop impacting issues label Jul 13, 2021
@csweichel
Copy link
Contributor

I fully agree this would be awesome to have, and it clearly supports our goals. It's not directly impacting the dev loop though, no?

@csweichel csweichel removed the priority: high (dev loop impact) Gitpod development loop impacting issues label Jul 13, 2021
@akosyakov
Copy link
Member Author

When someone works on upgrade to VS Code or new integration it does, but agree that it does not impact full team.

@csweichel
Copy link
Contributor

/schedule

@jeanp413 jeanp413 mentioned this issue Sep 1, 2021
Merged
@jeanp413 jeanp413 mentioned this issue Sep 20, 2021
Merged
@jeanp413 jeanp413 mentioned this issue Oct 7, 2021
Merged
@loujaybee loujaybee moved this to In Progress in 🚀 IDE Team Oct 20, 2021
@akosyakov
Copy link
Member Author

We merged our first test, not we need to setup nightly job for staging which run it.

@csweichel Should https://github.com/gitpod-io/gitpod/blob/main/.werft/run-integration-tests.yaml be used as a template?

@jeanp413 jeanp413 mentioned this issue Dec 29, 2021
Merged
@loujaybee loujaybee moved this from Done to In Progress in 🚀 IDE Team Jan 10, 2022
@akosyakov akosyakov moved this from In Progress to Awaiting Deployment in 🚀 IDE Team Jan 19, 2022
@jeanp413 jeanp413 moved this from Awaiting Deployment to In Progress in 🚀 IDE Team Jan 19, 2022
@akosyakov akosyakov moved this from In Progress to In Review in 🚀 IDE Team Jan 26, 2022
@loujaybee loujaybee mentioned this issue Feb 3, 2022
Closed
3 tasks
@akosyakov akosyakov changed the title Code integration testing [code] integration test cut-through Mar 1, 2022
@akosyakov
Copy link
Member Author

What left here? Reporting to slack channel nightly and fixing python test?

@jeanp413
Copy link
Member

jeanp413 commented Mar 2, 2022

yes, all those three.

@jeanp413
Copy link
Member

jeanp413 commented Mar 7, 2022 •
edited
Loading

  • Fix python tests
  • Enable select stable or insiders
  • Slack notification

@akosyakov akosyakov moved this from In Review to Awaiting Deployment in 🚀 IDE Team Mar 8, 2022
This was referenced Mar 8, 2022
Merged
Merged
@akosyakov
Copy link
Member Author

@jeanp413 is it done?

@jeanp413
Copy link
Member

yes, closing this.

@jeanp413 jeanp413 moved this from Awaiting Deployment to Done in 🚀 IDE Team Mar 15, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jeanp413 jeanp413

Labels
aspect: testing Anything related to testing Gitpod manually, automated integration tests or even unit tests editor: code (browser) meta: never-stale This issue can never become stale team: IDE
Projects
🚀 IDE Team
Status: Done
Milestone
No milestone
Development

No branches or pull requests
5 participants
@JanKoehnlein @akosyakov @csweichel @jeanp413 @roboquat