A mocked provider lets a Terraform test supply controlled resource and data values without making the provider’s real remote calls.
This can make tests faster and isolate a module’s expression and interface behavior. It cannot prove that actual credentials work, a quota is sufficient or the real API accepts an argument combination. Choose integration tests for those boundaries and plan cleanup for anything they create. Keep fixture values varied enough to catch a hard-coded answer. The browser provider itself is a teaching model, so passing its tests is evidence about the declared lab behavior and never proof of a deployment on a real platform.
A mock isolates a contract while leaving remote behavior unproven.