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
At the start of April 2022 git released a new non-major version that includes a new check, that fails pre-commit-terraform runtime (#370)
I'd like to not pin minor and patch versions of deps to avoid extra maintenance and security issues. At the same time, something can happen with deps, and we got a runtime error. So, we need to run runtime tests.
Need to add steps that go inside the build image and do the next things:
2.1. git clone repo with pre-commit-terraform test cases (subdir in tests/, in future, can be moved to separate repo)
2.2. Prepare to run pre-commit: cd pre-commit-terraform/tests, rm -rf ../.git, git init, git add -A
2.3. For each hook: Run pre-commit run -a HOOK_NAME and check that the output result is the same as expected.
I suppose that it can be done via bats-core (check Add unit-tests that will found problems with new code #303 for additional info)
So, from text above, we need to:
Add terraform code (valid and not) that we will test
Add tests, that will check that pre-commit run -a HOOK_NAME output is OK
The text was updated successfully, but these errors were encountered:
What problem are you facing?
At the start of April 2022
git
released a new non-major version that includes a new check, that failspre-commit-terraform
runtime (#370)I'd like to not pin minor and patch versions of deps to avoid extra maintenance and security issues. At the same time, something can happen with deps, and we got a runtime error. So, we need to run runtime tests.
How I see the realization of integration tests:
2.1.
git clone
repo withpre-commit-terraform
test cases (subdir intests/
, in future, can be moved to separate repo)2.2. Prepare to run pre-commit:
cd pre-commit-terraform/tests
,rm -rf ../.git
,git init
,git add -A
2.3. For each hook: Run
pre-commit run -a HOOK_NAME
and check that the output result is the same as expected.I suppose that it can be done via
bats-core
(check Add unit-tests that will found problems with new code #303 for additional info)So, from text above, we need to:
pre-commit run -a HOOK_NAME
output is OKThe text was updated successfully, but these errors were encountered: