how to disable core.debug in testing

[tianhaoz95]

Is there a way to disable core.debug when I am running jest locally? It is not so helpful to have all the logs on when running regression test.

[bryanmacfarlane]

The current model is for the action to emit the output and the runner to conditionally add to logs based on setting.

Can you clarify whether you want a way to silence during E2E testing or unit testing etc...?

[tianhaoz95]

Unit testing. For a node.js action, locally when i run jest --quiet, if I have some core.debug in my code, it will still print out to my console. I am guessing it is because jest doesn't recognize lower level logging. Is there a way that I can set some environment variable ACTION_LOG=false to disable that? I know that setting GitHub action secret can do that, but is there a equivalent locally?

[xt0rted]

I think this is a duplicate of #118

[tianhaoz95]

@xt0rted I think you are right. What is the final decision? jest config or some alternative?

[ericsciple]

would mocking the core module make more sense?

[ericsciple]

Example here where core is mocked out specifically to capture info.

Example here where core is mocked out to control the function results.

Users can leverage mocking tools to fit their specific needs.

[bryanmacfarlane]

Assigning to myself to update docs and guidance pointing to the examples ☝️

[thboop]

dupe of #118