![]() I noticed we had two mechanisms for unit test override. One that dropped a sentinel into the env var, and another with a struct member on TestCase. This consolidates the two, using the cleaner struct member internal mechanism and the nicer `resource.UnitTest()` entry point. |
||
---|---|---|
.. | ||
error.go | ||
id.go | ||
id_test.go | ||
map.go | ||
map_test.go | ||
resource.go | ||
state.go | ||
state_test.go | ||
testing.go | ||
testing_config.go | ||
testing_import_state.go | ||
testing_import_state_test.go | ||
testing_test.go | ||
wait.go | ||
wait_test.go |