awsrm VS terratest

It's because I build the tooling in way that Terraform resource names, such as aws_vpc, aws_instance, aws_iam_role, etc. can be used to find resources (with awsls) and delete them (with awsrm), instead of using the to me not so familiar and inconsistent AWS CLI (or CloudFormation) resource names with commands, such as aws ec2 describe-vpcs or aws ec2 delete-vpc (in some cases it's list instead of describe, e.g., for roles it's aws iam list-roles, which is hard to remember).

Terraform provides a built-in testing framework to validate your project. The testing framework supports both unit and integration tests. It handles unit tests by creating a deployment plan and running the tests against that plan. While Terraform's testing framework allows you to validate basic properties, you may need to write more advanced tests to verify your virtual machines are set up correctly. You can create advanced tests using open source testing tools like Terratest and Kitchen-Terraform.

Before using a module in production, make sure to test it in isolated environments. You can use tools like Terratest to write automated tests for your modules. This ensures they work as expected in different scenarios.

The Terratest Go library leverages this to define a variety of test cases used to test Docker images, cloud infrastructure defined for AWS, Azure, GCP, Kubernetes, and many more.

Terratest is a Go library that provides tools and patterns for testing infrastructure, with first-class support for Terraform, Packer, Docker, Kubernetes, and more. It's used to write automated tests for your infrastructure code.

I think I found it. This is the one right? https://github.com/gruntwork-io/terratest/

What it does in parallel is basically init/plan/show using terratest on every subdirectory on your repository tree or provided paths. The output is either a JSON summary or a custom made Junit XML test file you can ingest into your tests reader. It took it around 8 minutes to map the entirety of our bloated repository.

You could deploy to a separate account (usually dev first), you can use terratest, you could try something like LocalStack. I dare say there’s other methods.

Was wondering if anyone has tried https://github.com/gruntwork-io/terratest to test their infrastructure. I like it because I can write golang tests! Thats a big plus for me.

Once there is a CI pipeline for delivering infra changes you can add static code analysis tools (checkov) and even start testing changes (terratest)