When running Testplane in CLI, in some cases it's convenient to see what steps are running now, similarly to the "history" feature in the HTML Reporter. This would allow users that don't rely on HTML Reporter to see history & locate problems easier.
Describe the solution you'd like
Test steps are logged in CLI.
It would be nice to think what logging levels we want to have in general, what other info can be useful for the end user and how these logging levels would be convenient to use.
Right now we have multiple points where logs can be enabled, e.g. system.debug, DEBUG=..., etc.
Contribution
Describe the user story
When running Testplane in CLI, in some cases it's convenient to see what steps are running now, similarly to the "history" feature in the HTML Reporter. This would allow users that don't rely on HTML Reporter to see history & locate problems easier.
Describe the solution you'd like
Test steps are logged in CLI.
It would be nice to think what logging levels we want to have in general, what other info can be useful for the end user and how these logging levels would be convenient to use.
Right now we have multiple points where logs can be enabled, e.g.
system.debug,DEBUG=..., etc.Describe the drawbacks of your solution
No response
Describe alternatives you've considered
No response