Simplify LWRP tests
Currently we have the step_into
clause scattered among our tests in order to test the LWRPs. We also have already build chefspec matchers for these LWRPs.
To reduce the need for us to use step_into, we should:
- For each LWRP create a recipe in our fixtures that exercises everything about the LWRP we would want to test
- Write a test for the LWRP, that steps_into it, and converges on the LWRPs fixture test (this would be the only test file that needs to step into the LWRP)
- Ensure all our LWRPs have matchers defined
- Use the matchers in all other tests to avoid needing to 'step_into' the LWRP.
cc\ @balasankarc
Custom resources, and status of testing:
-
crond -
job
-
-
gitlab-ee - !3016 (merged) -
postgresql_fdw_user_mapping -
pgbouncer_user -
postgresql_fdw
-
-
gitlab -
puma_config - !3016 (merged)
-
-
letsencrypt -
certificate
-
-
package -
templatesymlink - !3001 (merged) -
env_dir - !2998 (merged) -
account - !2979 (merged) -
storage_directory - !2979 (merged) -
sysctl - !2979 (merged)
-
-
postgresql - !3005 (merged) -
database -
query -
schema -
user -
extension
-
Edited by Balasankar 'Balu' C