-
Notifications
You must be signed in to change notification settings - Fork 19
feat: initial testing framework (PSKD-1682) #265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Signed-off-by: chjmil <[email protected]>
Signed-off-by: chjmil <[email protected]>
Signed-off-by: chjmil <[email protected]>
Signed-off-by: chjmil <[email protected]>
Signed-off-by: chjmil <[email protected]>
Signed-off-by: chjmil <[email protected]>
Signed-off-by: chjmil <[email protected]>
Signed-off-by: chjmil <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pulled this branch content and:
Successfully built the viya4-iac-gcp-terratest image using the Dockerfile.terratest file using the documented docker build command.
Ran a set of commands from the TerratestDockerUsage.md file including
- Running the Plan tests
- Running the Apply tests
- Running a Specific test based on name regex
The output from each execution was consistent with expectations based on go test output and the visible annotations.
Adding the terratest unit testing framework. This framework mirrors the one in AWS and Azure.
One difference is that GCP expects the credentials to be stored in a file rather than exported variables. This caused some changes in the GitHub workflow.