Optional
aftCfg: AftConfigOptional
api: JiraApiPrivate
Readonly
_apiPrivate
Readonly
_closePrivate
Readonly
_logsPrivate
Readonly
_opencalled by the parent ReportingManager
on load to allow any plugins to configure
themselves for a new logger
the name of the ReportingManager
instance calling dispose
allows for filtering out of erroneous information from logs by assigning values to different types of logging. the purpose of each log level is as follows:
trace
- used when logging low-level debug events that occur within a loopdebug
- used for debug logging that does not run within a loop or at a high frequencyinfo
- used for informational events providing current state of a systemstep
- used within a test to denote where within the test steps we arewarn
- used for unexpected errors that are recoverablepass
- used to indicate the success of a test expectation or assertionfail
- used to indicate the failure of a test expectation or assertionerror
- used for unexpected errors that are not recoverablenone
- used when no logging is desired (disables logging)Private
_closePrivate
_openGenerated using TypeDoc
this plugin uses the following configuration to control its operation via
aftconfig.json
NOTE: