Go to discover tests directory after login

[falconizmi]

Pull Request Checklist

• implement the feature
• extend the test coverage
• include a release note

[falconizmi]

Solves issue #803
for tmt try, if user run tmt try --login, it wont run any tests as its how login was implemented:
-l, --login Log into the guest only, do not run any
and he will be logged in to worktree path

So the user needs to run tmt run -tests NAME then, when he will be asked what to do next, choose login option and in that case, he will be logged in test path

[falconizmi]

Okay, I have here some failures because the test path, that I expect, is /var/tmp/tmt/run-XXX/something/discover/default-0/, but instead when we have this test case:
plan

summary: Basic smoke test
execute:
    how: tmt
    script: tmt --help

and run it with this tmt command:
tmt run -a provision -h local --feeling-safe
and after the run take a look in the directory /var/tmp/tmt/run-XXX/something/discover/, there is no default-0/ directery.
And in the check, there is after that command tmt run -l login -c true, which will fail, because it executes the last run that doesnt have folder default-0/
(or at least that what I think now)

Fixed by commit: 8f946c9

[martinhoyer]

I don't have much experience with tmt try code, but tried it and this /bin/true approach seems to work :)

[psss]

Thanks for implementing this. Looks good. I just think that we do not have to exercise the /bin/true check when there are no tests. Adjusted in b67e154. Please have a look if the change is ok. It would be also good to add at least a basic test coverage and mention this in release notes as this feature was requested by users and they should learn about this good news :-)