You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 7, 2023. It is now read-only.
Our current methodology for testing PRs is to run any tests that are changed and if a role is changed, just run the improved-sanity-test. It's better than nothing, but less than ideal.
I propose we add some logic to .test_director to determine which roles have changed and run them individually in a dummy playbook. This would allow us to find dependency issues (because we are sloppy with the variable namespace and assume A LOT about what is available), but would also generally improve the kind of testing we are doing on PRs.
This could also grow pretty easily to determining which tests are utilizing the roles and running those tests as well.
The text was updated successfully, but these errors were encountered:
Our current methodology for testing PRs is to run any tests that are changed and if a role is changed, just run the
improved-sanity-test
. It's better than nothing, but less than ideal.I propose we add some logic to
.test_director
to determine which roles have changed and run them individually in a dummy playbook. This would allow us to find dependency issues (because we are sloppy with the variable namespace and assume A LOT about what is available), but would also generally improve the kind of testing we are doing on PRs.This could also grow pretty easily to determining which tests are utilizing the roles and running those tests as well.
The text was updated successfully, but these errors were encountered: