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
I have a long running test action, and I'd like to see the output from it as it runs, rather than having to wait till the command finishes before Garden shows me the logs.
I tried running garden test with the --interactive flag, but to my surprise it didn't result in the logs being printed live. If the intended behaviour of the --interactive flag for garden test (with a single test selected) is for it to print the logs as they arrive, then this issue can be closed, and a bug report can be opened instead.
What should the user be able to do?
garden test <test name> --tail
Similar to the --interactive flag, this should only work if a single test is specified.
When Garden begins executing the specified test, it should print the logs of the test action as they arrive.
Why do they want to do this? What problem does it solve?
I want this so that I can react to test failures as they occur, rather than 10+ minutes later once all the integration tests have finished running.
How important is this feature for you/your team?
🌹 It’s a nice to have, but nice things are nice 🙂
The text was updated successfully, but these errors were encountered:
Feature Request
Background / Motivation
I have a long running test action, and I'd like to see the output from it as it runs, rather than having to wait till the command finishes before Garden shows me the logs.
I tried running
garden test
with the--interactive
flag, but to my surprise it didn't result in the logs being printed live. If the intended behaviour of the--interactive
flag forgarden test
(with a single test selected) is for it to print the logs as they arrive, then this issue can be closed, and a bug report can be opened instead.What should the user be able to do?
garden test <test name> --tail
Similar to the
--interactive
flag, this should only work if a single test is specified.When Garden begins executing the specified test, it should print the logs of the test action as they arrive.
Why do they want to do this? What problem does it solve?
I want this so that I can react to test failures as they occur, rather than 10+ minutes later once all the integration tests have finished running.
How important is this feature for you/your team?
🌹 It’s a nice to have, but nice things are nice 🙂
The text was updated successfully, but these errors were encountered: