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
Pass arguments BaseCharmTest.setUpClass #257
Pass arguments BaseCharmTest.setUpClass #257
Conversation
Not doing so triggers an incorrect behavior leading to functional test failures as the application name is not set correctly. #256 https://review.opendev.org/#/c/712980/1
Codecov Report
@@ Coverage Diff @@
## master #257 +/- ##
==========================================
+ Coverage 20.35% 20.80% +0.44%
==========================================
Files 131 131
Lines 7250 7250
==========================================
+ Hits 1476 1508 +32
+ Misses 5774 5742 -32
Continue to review full report at Codecov.
|
This is a great catch. It's also a breaking change? It would be good to see some test runs against a few charms to check that there's no unexpected behaviour in other tests that may cause us trouble -- we're 3 days from freeze! Please could we test against, say (in a bastion):
and verify there's no weird behaviour. Note. I may be being over-cautious here, in which case, please feel free to comment! |
Zaza tests are already implemented Change-Id: I59b52f3736029e134856a2bee69dd2b5037e9d52 Closes-Bug: #1828424 Func-Test-PR: openstack-charmers/zaza-openstack-tests#257
* Update charm-designate-bind from branch 'master' - Remove Amulet leftovers Zaza tests are already implemented Change-Id: I59b52f3736029e134856a2bee69dd2b5037e9d52 Closes-Bug: #1828424 Func-Test-PR: openstack-charmers/zaza-openstack-tests#257
@ajkavanagh The change that introduced the issue was done quite recently: 9cb7876e So I think it's not a breaking change as far as the older tests go but the ones merged between then and now might be affected. To find out whether any of them are I did the following:
There is a lesser possibility that some of those test cases began to pass after 9cb7876 was merged. This change managed to fix it for https://review.opendev.org/#/c/712980/ |
@dshcherb okay, I think we are probably pretty safe then. Let's get this merged :) |
Zaza tests are already implemented Change-Id: I59b52f3736029e134856a2bee69dd2b5037e9d52 Closes-Bug: #1828424 Func-Test-PR: openstack-charmers/zaza-openstack-tests#257
Not doing so triggers an incorrect behavior leading to functional test
failures as the application name is not set correctly.
#256
https://review.opendev.org/#/c/712980/1