adobe-type-tools
runner.py based tests too obscure
As I've been working on some reorganization I've spent way too much time trying to work through how to reproduce the command line equivalents of runner.py based tests. The command itself has a "verbose" option but even if you edit the "parent" test file by hand to add it I can't figure out where the output goes.
Many of the other AFDKO tests print the args array on failure. It would be greatly preferable if the runner-based tests did as well.
https://github.com/adobe-type-tools/afdko/blob/develop/tests/runner.py#L98-L99
Could maybe modify this (logging level > debug) and make use of pytest's caplog or --log-cli-level to get better reporting?
@josh-hadley Not sure if that's a solution or a work-around. The typical modern test philosophy is don't print anything when there isn't a problem and print useful information when there is. Ideally we would only print the args array when a test fails.
Using --log-cli-level (when invoking pytest) would be a temporary workaround. Employing caplog in the test code would be a better long-term solution for printing the args only on failure. It might require some coordination between runner.py and the calling tests but I believe it would work (same way as other tests can use capsys to print stderr/stdout on failure).