Skip to content
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

Rake e2e tests fail #15

Open
dtzar opened this issue Jan 25, 2018 · 5 comments
Open

Rake e2e tests fail #15

dtzar opened this issue Jan 25, 2018 · 5 comments

Comments

@dtzar
Copy link
Contributor

dtzar commented Jan 25, 2018

When you run rake e2e the tests fail with:

$$$$$$ Running command `terraform destroy -force -lock=true -lock-timeout=0s -input=false -no-color -parallelism=1 -refresh=true  -var-file=/tf-test/module/test/integration/fixtures/testing.tfvars /tf-test/module`    
       Error: Required variable not set: load_balancer_backend_address_pool_ids    
       Error: Required variable not set: vnet_subnet_id

These are not able to be specified since they are an output from a different module. The module code works flawlessly. Therefore, the test framework / code needs to be updated to accomodate this scenario.

@dtzar dtzar changed the title Rake e2e tests fail - test framework problem Rake e2e tests fail Jan 25, 2018
@dcaro
Copy link
Contributor

dcaro commented Jan 26, 2018

@metacpp can you have a look at this?

@metacpp
Copy link

metacpp commented Jan 26, 2018

Why the test case is broken here? Regression ? @VaijanathB can you take a look at the test case you added here ?

@metacpp
Copy link

metacpp commented Jan 26, 2018

@dtzar I have enabled the branch protection here, if the travis fails, it will block the merge.

@metacpp
Copy link

metacpp commented Aug 27, 2018

We've migrated the test framework to Terratest in #18. There's still failure after merge:
https://travis-ci.org/Azure/terraform-azurerm-computegroup/builds/420907668

@JunyiYi please take a look at this issue.

@foreverXZC
Copy link
Contributor

@metacpp When I was trying e2e test locally using docker, sometimes I also met this problem. However, if I restart the test, it may pass the build. I wonder why the tests are not consistent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants