Closed llaville closed 2 years ago
I found another side effect of wrong implementation (using TEXT_REPORTER
, rather than TAP_REPORTER
)
When you want to deactivate TEXT_REPORTER for remote GA run and activate it for local run (debugging purpose), you have TAP reporter also generated locally.
Real Use Case may be found below (workaround for local run vs GA run)
Seems to be a typo, it should be TAP_REPORTER in the code :)
Describe the bug The configuration detailed on page https://github.com/nvuillam/mega-linter/blob/master/docs/reporters/TapReporter.md#configuration does not match the current v4.45 implementation (https://github.com/nvuillam/mega-linter/blob/v4.45.0/megalinter/reporters/TapReporter.py#L21-L41)
To Reproduce Add nothing in
.mega-linter.yml
config file because, it's supposed to have TAP activated by defaultExpected behavior A
tap
sub-folder inreport
directory with tap logsScreenshots Nothing produced
Additional context Workaround is to set
TEXT_REPORTER: true