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

Fixes lp#1742222: intermittent failure in BundleDeployCharmStoreSuite.TestAddMetricCredentials #8287

Merged
merged 1 commit into from
Jan 15, 2018

Conversation

anastasiamac
Copy link
Contributor

Description of change

This change brings in a new testing stub check that allows to check for calls made irrespective of their order.
This PR also uses this new call in a test that failed intermittently, specifically because it did not matter in what order the calls were made to the stub... We only cared about the fact that calls were made.

QA steps

BundleDeployCharmStoreSuite.TestAddMetricCredentials does not fail.

Bug reference

https://bugs.launchpad.net/juju/+bug/1742222

@anastasiamac
Copy link
Contributor Author

Just to clarify - the order here does not matter because the test has changed... Originally, we were uploading one charm, so there was only one call made.
We now upload 'mysql' charm, 'wordpress' charm alone and 'wordpress' charm in a bundle with default plan, so there are 3 calls made to the stub and their order may vary based on which upload call wins.
As per bug comment # 2, this change in a unit test was introduced in 081b5d3

@anastasiamac
Copy link
Contributor Author

$$merge$$

@jujubot
Copy link
Collaborator

jujubot commented Jan 15, 2018

Status: merge request accepted. Url: http://ci.jujucharms.com/job/github-merge-juju

@jujubot jujubot merged commit ecd7f2c into juju:develop Jan 15, 2018
@anastasiamac anastasiamac deleted the testing-call-order-lp1742222 branch January 15, 2018 06:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants