Patently false. Terraform has had an excellent test suite since 2014.
To make a python metaphor, if cpython had a testing suite but pytest didn't exist then people wouldn't be able to test their own python code. That's kind of the situation with Terraform right now- you can't test your code using just the Terraform tools, you have to rely on Terratest which was written by Gruntwork. Hashicorp has spent years relying on the open source community to fill those gaps, which Gruntwork has done very nicely.
Hashicorp even recommends Terratest for testing: https://www.hashicorp.com/blog/testing-hashicorp-terraform
Saying "Terraform doesn't have a test suite" is not miscommunication, it is misinformation, plain and simple - the same as most of the other things I have been correcting this week (not least from the same poster in this thread - someone who's clearly has an axe to grind).
It’s actually not a guesstimate about what actions will be taken, it’s a guesstimate of the state that will result from those actions without any reference to ordering or “actions” as a cloud API would understand them - the plan is purely in terms of CRUD on Terraform provider resources and provisioners.
This may seem like a nit, but it fundamentally changes what Terraform is capable of doing in a single pass without external coordination.
They have experimental support: https://developer.hashicorp.com/terraform/language/modules/t...
Beyond that, I know some of these companies tried to be contributors to Terraform itself but were ghosted by Hashicorp.
At the same time there's only a handful of regular contributors to Terraform[1]. It would not be hard for these companies to provide more resources to Terraform than Hashicorp is.
https://github.com/hashicorp/terraform/pulse/monthly