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

Include debug into devworkspace happy path test #20537

Closed
sleshchenko opened this issue Sep 24, 2021 · 2 comments
Closed

Include debug into devworkspace happy path test #20537

sleshchenko opened this issue Sep 24, 2021 · 2 comments
Assignees
Labels
area/qe kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. sprint/current

Comments

@sleshchenko
Copy link
Member

sleshchenko commented Sep 24, 2021

Is your task related to a problem? Please describe

Debug is not included into happy path test

Describe the solution you'd like

Include debug into devworkspace happy path test. it includes
Display source code changes in the running application, Validation of debug functionality
More see #20385 (comment).

Describe alternatives you've considered

No response

Additional context

Depends on #20536

@sleshchenko sleshchenko added kind/task Internal things, technical debt, and to-do tasks to be performed. team/controller area/qe labels Sep 24, 2021
@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 24, 2021
@sleshchenko sleshchenko added the status/blocked Issue that can’t be moved forward. Must include a comment on the reason for the blockage. label Sep 24, 2021
@dkwon17 dkwon17 added severity/P1 Has a major impact to usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Sep 27, 2021
@sleshchenko sleshchenko added sprint/current and removed status/blocked Issue that can’t be moved forward. Must include a comment on the reason for the blockage. labels Oct 29, 2021
@ibuziuk
Copy link
Member

ibuziuk commented Nov 5, 2021

@musienko-maxim could you please clarify the status of the issue? should we move it to the next sprint?

@musienko-maxim
Copy link
Contributor

It was included in the PR: #20948

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/qe kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P1 Has a major impact to usage or development of the system. sprint/current
Projects
None yet
Development

No branches or pull requests

5 participants