Add configuration option to disable/enable multiple commands logging #8296
Labels
stage: proposal 💡
No work has been done of this issue
type: enhancement
Requested enhancement of existing feature
This issue relates to the #3087
Current behavior:
I have many commands that are not desired to be logged: setting states, clearing fields, etc. Mostly it relates to the negative cases when I do smth repeatable. For example, iterate through the array with invalid characters and type them into the input field:
(some assertions will be added)
In this case, if logging is not turned off, the left side log looks very "crowded". I need information only about characters that are typed.
So, about 70% of commands have
{log: false}
option in my tests. It takes time to add this option and code looks not so pretty.Desired behavior:
I have a proposition:
{log: }
option forcontext()
andit().
So, then users have the ability to enable/disable logging in different scopes.
Versions
4.12.1
The text was updated successfully, but these errors were encountered: