You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Let's say I do tmt try and I see that the test failed due command not found. I can easily fix that by adding missing dependency to 'require' or 'recommend'.
But to test again I need:
Press 't' which will discover test and dependencies again. Then it will FAIL again as nothing installed new dependencies
Press 'p' to run prepare step, which will install new dependencies (and will run all other prepare phases)
Press 't' to run the test again
Note that running 'prepare' again my fail as its phases aren't expected to be idempotent (in "real" tmt runs they are executed just once) or they just waste time (if they run too long).
I'd expect that 't' should be able to detect that require/recommend has changed and run just the necessary install phase without any additional user output. The flow will then be: 1. Press 't' to reflect changes and run test again.
The text was updated successfully, but these errors were encountered:
Let's say I do
tmt try
and I see that the test failed duecommand not found
. I can easily fix that by adding missing dependency to 'require' or 'recommend'.But to test again I need:
Note that running 'prepare' again my fail as its phases aren't expected to be idempotent (in "real" tmt runs they are executed just once) or they just waste time (if they run too long).
I'd expect that 't' should be able to detect that require/recommend has changed and run just the necessary install phase without any additional user output. The flow will then be: 1. Press 't' to reflect changes and run test again.
The text was updated successfully, but these errors were encountered: