Consider making terratest output readable

[jkremser]

Because of the fact that terratests are run in parallel and produce a lot of log messages when doing the polling mechanisms (those waitUntilX functions), it's almost impossible to find out the root cause of the issue why some test is red.

Gruntwork provides a tool that produces separate log files for each test w/o any interleaving, it's called terratest_log_parser They also provide an example how to use it together with CircleCI. Here is an example of circle.ci config: https://github.com/gruntwork-io/kubergrunt/blob/master/.circleci/config.yml#L42:L54

They upload the separate log files into artifact repository that pertains to the job. GHA has something similar

links:

• https://terratest.gruntwork.io/docs/testing-best-practices/debugging-interleaved-test-output/
• https://github.com/actions/upload-artifact

[AugustasV]

Will take a look into that

[jkremser]

@AugustasV thanks!