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

Create script for provisioning required test workspace #14385

Closed
Ohrimenko1988 opened this issue Aug 29, 2019 · 3 comments
Closed

Create script for provisioning required test workspace #14385

Ohrimenko1988 opened this issue Aug 29, 2019 · 3 comments
Assignees
@Ohrimenko1988
Labels
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. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.
Milestone
Backlog - QE

Comments

@Ohrimenko1988
Copy link
Contributor

Is your task related to a problem? Please describe.

Now for launching the "happy-path" test we should manually provision the workspace

Describe the solution you'd like

Automate these steps by script
@Ohrimenko1988 Ohrimenko1988 added status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it. kind/task Internal things, technical debt, and to-do tasks to be performed. team/che-qe labels Aug 29, 2019
@Ohrimenko1988 Ohrimenko1988 self-assigned this Aug 29, 2019
@dmytro-ndp
Copy link
Contributor

It's actually a requirement of Happy path test scenario to run test workspace using chectl #12728:
Screenshot from 2019-08-29 17-15-00

@dmytro-ndp
Copy link
Contributor

There is an ability to run shell command from typescript https://stackoverflow.com/a/49701572/2556329
It could be used to run chectl start:workspace command.

@rhopp rhopp added this to the Backlog - QE milestone Sep 23, 2019
@che-bot
Copy link
Contributor

che-bot commented Mar 25, 2020

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 Mar 25, 2020
@che-bot che-bot closed this as completed Apr 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Ohrimenko1988 Ohrimenko1988

Labels
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. status/open-for-dev An issue has had its specification reviewed and confirmed. Waiting for an engineer to take it.
Projects
None yet
Milestone
Backlog - QE
Development

No branches or pull requests
4 participants
@dmytro-ndp @rhopp @Ohrimenko1988 @che-bot