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

odo test - execute test command defined in devfile #6070

Open
1 task
kadel opened this issue Aug 31, 2022 · 5 comments
Open
1 task

odo test - execute test command defined in devfile #6070

kadel opened this issue Aug 31, 2022 · 5 comments
Labels
kind/user-story An issue of user-story kind lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Medium Nice to have issue. Getting it done before priority changes would be great.

Comments

@kadel
Copy link
Member

kadel commented Aug 31, 2022

/kind user-story

User Story

As an odo user I want to be able to run test command as defined in devfile.yaml so that I can run predefined tests and see results.

Acceptance Criteria

  • odo test command should run the default kind: test command as defined in the devfile.yaml

Links

The logic behind the command execution should be the same as in #6568 The only difference is that #6568 odo test executes default test command, and odo run is more generic to allow execution of any command from devfile.

It might be good idea to implement #6568 first, and then reuse the same logic for odo test

/kind user-story

@openshift-ci openshift-ci bot added the kind/user-story An issue of user-story kind label Aug 31, 2022
@rm3l rm3l added this to odo Project Aug 31, 2022
@kadel kadel changed the title run test command odo test - execute test command defined in devfile Feb 8, 2023
@kadel kadel added the priority/Medium Nice to have issue. Getting it done before priority changes would be great. label Feb 23, 2023
@rm3l rm3l removed this from after v3.0.0 Jun 29, 2023
@rm3l rm3l removed the needs-triage Indicates an issue or PR lacks a `triage/*` and requires one. label Jun 29, 2023
@rm3l
Copy link
Member

rm3l commented Jul 6, 2023

Grooming (Jul 6, 2023)

  • Determine the test command to run (default or single non-default one)
  • Reuse the low-level logic of odo run (which makes sure the Dev session is started, executes the command, grabs the logs, ...)

@github-actions
Copy link
Contributor

github-actions bot commented Oct 5, 2023

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 5, 2023
@rm3l
Copy link
Member

rm3l commented Oct 5, 2023

/remove-lifecycle stale

Still relevant.

@openshift-ci openshift-ci bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 5, 2023
Copy link
Contributor

github-actions bot commented Jan 4, 2024

A friendly reminder that this issue had no activity for 90 days. Stale issues will be closed after an additional 30 days of inactivity.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 4, 2024
@rm3l
Copy link
Member

rm3l commented Jan 4, 2024

/lifecycle frozen
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jan 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/user-story An issue of user-story kind lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/Medium Nice to have issue. Getting it done before priority changes would be great.
Projects
Status: No status
Development

No branches or pull requests

2 participants