testing-library

Currently there is no way to customize the terraform or terragrunt command you are running in each session when you go through the functions in terraform package, such as terraform.Apply or terraform.TgApplyAll if it isn't supported in terraform.Options. This is limiting if your code depends on flags like parallelism or terragrunt flags like --terragrunt-include-external-dependencies.

What is your question:

I'm sorta ashamed to admit it, but it's unclear to me how to use the async utils based on the docs. I've had to dig around a lot to figure it out. Could there be a few code examples added to the docs?

Describe the feature you'd like:

This should be a fairly short and sweet conversation (and possibly related to #201). I am a developer working on a fairly complex enterprise app. This app has pages with tons of form fields. While developing new features, I found myself filling out the same fields with the same values over and over again. To remedy this, I thought it would be a time saver to

Plugin version

v5

What problem do you want to solve?

Our current tests don't have any specific name or title to identify them. This makes it complicated to debug them, or differentiate the same test cases with different options, etc. Each test is represented by its code itself, which can be something really long, or duplicated between tests with the same code but different options