-
Notifications
You must be signed in to change notification settings - Fork 123
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
Implement tmt try
for interactive sessions
#2443
Conversation
What should happen after aborted menu (eg. ctrl+d or ctrl+c)? Currently provisioned machine keeps running. |
Hello. Looks great. @psss Do you have plans to allow modules to extend menu of provided choices? For example, minute module can provide 2 types of reboot and other stuff. |
Another one: people are use to use 1minutetip so maybe use r(etest) instead of t(est). And why I should, as a user who work on test, should take care about discovery and execute step? In case that I change fmf/tmt metadata, should I rerun discovery step manually from menu? |
/packit test --identifier full |
/packit test --identifier full |
So... finally all tests are green and the checklist is done. @lukaszachy, @thrix, @happz, @kkaarreell, @KwisatzHaderach, @janhavlin, @therazix, please have a look & give it a |
/packit test --identifier full |
/packit test --identifier full |
Basic functionality for the new `tmt try` command to be used for test development in an interactive session. Supports running tests from the current working directory as well as quick experimenting with selected distro image and provision method. Simple user plan config is included as well.
/packit test --identifier full |
Basic functionality for the new
tmt try
command to be used for test development in an interactive session. Supports running tests from the current working directory as well as quick experimenting with selected distro image and provision method. Simple user plan config is included as well.Fix #606 and https://issues.redhat.com/browse/TT-245
Pull Request Checklist