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
User story
As a framework user, I want to be able to extend the default behavior of LoggingReporter to meet my specific needs. This includes logging the execution of TestActions, particularly in failure cases, as well as logging the execution of SequencesBeforeTest and SequencesAfterTest. Currently, none of these events trigger callbacks to LoggingReporter.
To address this, the proposal is to enhance the LoggingReporter (or one of its related interfaces) by adding the following methods:
User story
As a framework user, I want to be able to extend the default behavior of LoggingReporter to meet my specific needs. This includes logging the execution of TestActions, particularly in failure cases, as well as logging the execution of SequencesBeforeTest and SequencesAfterTest. Currently, none of these events trigger callbacks to LoggingReporter.
To address this, the proposal is to enhance the LoggingReporter (or one of its related interfaces) by adding the following methods:
The text was updated successfully, but these errors were encountered: