console logging not clear about tryorama HOT 6 CLOSED

Adapted to your command, it's TRYORAMA_LOG_LEVEL=debug npm test.

Also see the message above your's on discord https://discord.com/channels/727959104777224303/776952534873931806/1072575344336437268

On Monday I'll release.

from tryorama.

doesnt make a difference if run the command you suggest... console logs are lost.. its much harder to diagnose what is going on when your tests fail without being able to log intermediate states and steps. even a file log would help

from tryorama.

Then I need a repro. two people have tested this this week.

Your npm test is calling another npm t -w tests, which in turn calls some foreach stuff - perhaps that spawns a new shell without the log level env var set?

from tryorama.

the test above is from the scaffolding tool with the forum template example .. just added one console.log to a test scenario. also tried with another happ using a single test scenario..
i noticed Connor is using some kind of logger library.. perhaps he had the same problem?

from tryorama.

ok the scaffolding tool has been updated and logging works again

from tryorama.

I'm glad it's resolved, although it's still mysterious how these logs can have been swallowed.

from tryorama.