PingOne testing strategy

[patrickcping]

Multi-region acceptance testing
The PingOne provider runs a nightly acceptance test, and also runs acceptance tests on merge into the main branch. The acceptance tests run every single test case in every region (EU, NA, APAC, CA) to ensure that region-specific nuances are accounted for

Test cases
The following test cases are expected to be defined:

1. New environment test case - Where multiple instances of a resource can be created in an environment (1 to many relationship), this test case is designed to test creation of the first object in a new environment. The purpose of this test is to identify potential race conditions that need additional retry logic. Example
2. Existing environment test cases - Where multiple instances of a resource can be created in an environment (1 to many relationship), this test case is designed to test the bulk of the attribute/use case tests, to avoid many simultaneous environment creations that slow the acceptance test routine. Where a single instance of a resource is the limit, then all tests will use a new environment strategy as above. Example
3. Use case testing with "full" and "minimal" data models - This is a test that creates resources (and validates) the "full" data model (defining custom Required, Optional and validating Computed data in the schema; to validate all schema items have been mapped to the API successfully), and the "minimal" data model (defining custom Required, leaving default Optional and validating Computed attributes; to validate the TF schema has the correct defaults). The test should have steps to create both from fresh, and test modifications from one to the other. Example
4. Invalid data / custom errors - To test whether custom errors are successfully overridden in response to bad data input. Example
5. Bootstrapping specific - To test whether creates/updates behave correctly with new resources alongside bootstrapped resources. Example

Check for destroy confirmation
The PingOne provider will be enforcing the CheckDestroy implementation, to ensure that the delete routine works successfully. Example

[patrickcping]

#85 introduces regular multi-region acceptance test CI. That PR resolves part of this issue, but not all.