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

[TS-SELENIUM] Cover "devfile" stacks by E2E tests #13531

Closed
Ohrimenko1988 opened this issue Jun 12, 2019 · 4 comments
Closed

[TS-SELENIUM] Cover "devfile" stacks by E2E tests #13531

Ohrimenko1988 opened this issue Jun 12, 2019 · 4 comments
Labels
area/qe kind/task Internal things, technical debt, and to-do tasks to be performed. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Milestone

Comments

@Ohrimenko1988
Copy link
Contributor

Ohrimenko1988 commented Jun 12, 2019

Description

According to changes in the stacks config approach(switching to using devfiles #12924 #13517) we should validate behavior of stacks introduced on dashboard.

@Ohrimenko1988 Ohrimenko1988 added kind/task Internal things, technical debt, and to-do tasks to be performed. team/che-qe labels Jun 12, 2019
@rhopp rhopp added this to the Backlog - QE milestone Sep 23, 2019
@rhopp rhopp changed the title [TS-SELENIUM] Cover "devfile" tacks by E2E tests [TS-SELENIUM] Cover "devfile" stacks by E2E tests Sep 23, 2019
@rhopp rhopp added the Epic label Sep 23, 2019
@rhopp
Copy link
Contributor

rhopp commented Sep 23, 2019

@Katka92 I know you were already working on this one. Could you please add the issues/PRs you were working on to this epic?

@Katka92
Copy link
Contributor

Katka92 commented Sep 23, 2019

@rhopp sure, I've create test for Java Vert.x. I don't have issue for that, PR is here: #14558 . More information about this test can be found in PR description.

@nickboldt nickboldt removed the Epic label Dec 5, 2019
@Katka92
Copy link
Contributor

Katka92 commented Jan 27, 2020

We have covered Vert.x stack too, Python Django stack is in progress.

@rhopp rhopp added the area/qe label May 11, 2020
@che-bot
Copy link
Contributor

che-bot commented Jan 4, 2021

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 Jan 4, 2021
@che-bot che-bot closed this as completed Jan 20, 2021
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. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

5 participants