Unity tests no longer show Serial output without verbose option

[torntrousers]

After an updated from v5 to PlatformIO Core, version 6.0.1 Serial output in tests no longer shows unless the verbose option is used.

For recreate see: https://community.platformio.org/t/unity-test-serial-print-output-gone/27800/3?u=torntrousers

[ivankravets]

Hi Anthony,

Thanks for the report. Indeed, this is a feature, not a bug. We don't print all junk from the testing frameworks and provide you by default only valuable information. The --verbose mode is the right solution. However, I agree, it prints now a ton of junk from the previous stages (build/upload).

So, what I propose. Allow passing multiple -v options:

• -v - makes testing verbose
• -vv - makes building and uploading verbose
• -vvv - makes building and uploading much more verbose.

Your thoughts?

[torntrousers]

having all the building etc type messages be moved from -v to -vv / -vvv would definately help.
it wasn't obvious to me how to set verbose mode when running test in vscode, something about project-tasks but it looked a bit complicated.

[torntrousers]

Honestly though, it seems a bit of a pain, why the change?

[ivankravets]

You can override it via pio test -v.

[torntrousers]

Mmm, not yet convinced that this is an improvement over the v5 behaviour. How do I set -v in vscode?

[ivankravets]

Thanks! The configuration option in INI has been removed. However, the multilevel verbosity is available for pio test command. Also, new "Verbose Test" command has been added platformio/platformio-node-helpers@6931b21
Will be a part of the next release of PlatformIO IDE for VSCode.

Meanwhile, you can declare custom target with pio test -v. It will be available in IDE in the Tasks view.

We also plan to create a separate Test View. Please subscribe to this feature platformio/platformio-vscode-ide#3168

[torntrousers]

None of those really seem great though when all i want is to see the test output so i can add debugging output while developing new code, like it used to. I suppose the separate Test View might help, but its not available yet.

[j4m3s]

I've run into the same issue. We write log output to std::cout, and it used to be visible in v5.x. It's now lost/ swallowed in v6.

The pio test -v option in v6.0.2 doesn't help with the noise unfortunately, it still shows all of the tests collected and skipped, and doesn't colour the individual test results etc.

FYI the link included in the comment above doesn't seem to point to anything about the verbosity level?:

A new configuration option is added https://docs.platformio.org/en/latest/projectconf/section_env_test.html#test-verbosity-level

You can also override it via pio test -v.

[ivankravets]

Yes, PlatformIO normalizes test results from multiple testing frameworks to the unified output. Typically, people don't use Unit Testing to debug their applications. If you need custom results output, please override https://github.com/platformio/platformio-core/blob/develop/platformio/test/runners/unity.py#L260

See https://docs.platformio.org/en/latest/advanced/unit-testing/frameworks/custom/index.html