odo test should have subcommand to list available tests to run with --test-command

[dgolovin]

/kind feature

Which functionality do you think we should add?

odo test run default test and in case there are many test commands 'odo test --test-command ` command can be used. In this case user have to go and find it in devfile. For IDE's it means parsing devfile and looking for commands in test group if I understand that correctly.

Would be good if odo test would be able to list available test commands as odo test list with -o json support as well.

Why is this needed?

For user that would be the same experience as as with other commands sub-commands odo has already. That would eliminate necessity to open devfile and search for it.

IDEs would be able to fetch list of available test commands for component without parsing devfile.

[kadel]

/priority low

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[kadel]

/reopen
/remove-lifecycle rotten
still valid

[openshift-ci]

@kadel: Reopened this issue.

In response to this:

/reopen
/remove-lifecycle rotten
still valid

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

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

/lifecycle stale

[kadel]

we first need to implement odo test in odo v3 (#6070)

[kadel]

/status blocked
by #6070

[github-actions]

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]

This issue was closed because it has been inactive for 30 days since being marked as stale.