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

Verify Che Code editor using typescript E2E tests #21463

Closed
dmytro-ndp opened this issue Jun 14, 2022 · 1 comment
Closed

Verify Che Code editor using typescript E2E tests #21463

dmytro-ndp opened this issue Jun 14, 2022 · 1 comment
Labels
area/qe kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.

Comments

@dmytro-ndp
Copy link
Contributor

dmytro-ndp commented Jun 14, 2022 •
edited
Loading

Is your task related to a problem? Please describe

We need to prepare to switch from Che-Theia to Che code editor in Eclipse Che 7.51

Describe the solution you'd like

Rewrite existed typescript E2E tests to be run against Che Code Editor.
Use https://github.com/redhat-developer/vscode-extension-tester library.

Subtasks:

Describe alternatives you've considered

No response

Additional context

No response
@dmytro-ndp dmytro-ndp added kind/task Internal things, technical debt, and to-do tasks to be performed. team/che-qe area/qe severity/P1 Has a major impact to usage or development of the system. labels Jun 14, 2022
@dmytro-ndp dmytro-ndp added kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. and removed kind/task Internal things, technical debt, and to-do tasks to be performed. labels Jun 28, 2022
@dmytro-ndp dmytro-ndp changed the title Test Che Code editor in typescript E2E tests Verify Che Code editor using typescript E2E tests Jul 5, 2022
@dmytro-ndp dmytro-ndp mentioned this issue Nov 1, 2022
Closed
@che-bot
Copy link
Contributor

che-bot commented Jun 7, 2023

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 7, 2023
@che-bot che-bot closed this as completed Jun 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/qe kind/epic A long-lived, PM-driven feature request. Must include a checklist of items that must be completed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nickboldt @dmytro-ndp @che-bot