Merge ~weii-wang/content-cache-charm:fix-integration-test into content-cache-charm:master
Status: | Merged |
---|---|
Approved by: | Haw Loeung |
Approved revision: | 152edecec75fe7037a9f8063309fc12daaac0612 |
Merged at revision: | 9a8fe20a0882a7bbd53e02edd565f1b107cd8a11 |
Proposed branch: | ~weii-wang/content-cache-charm:fix-integration-test |
Merge into: | content-cache-charm:master |
Diff against target: |
83 lines (+44/-3) 1 file modified
tests/integration/integration_test.py (+44/-3) |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Haw Loeung | +1 | Approve | |
Colin Watson (community) | Approve | ||
Canonical IS Reviewers | Pending | ||
Review via email:
|
Commit message
Use charmcraft to build charm in integration tests
The pytest-operator for integration testing uses `charm` instead of `charmcraft` to build reactive charm. `charm` uses the host environment to build the charm. when the host contains an incorrect version of Python, `charm` will package the incorrect Python package into the charm. `charmcraft` builds the charm using the LXD container with the appropriate Ubuntu image, so there is no such problem with `charmcraft`.
In this commit, change the integration test to call `charmcraft` instead of using `ops_test.
Description of the change
The pytest-operator for integration testing uses `charm` instead of `charmcraft` to build reactive charm. `charm` uses the host environment to build the charm. when the host contains an incorrect version of Python, `charm` will package the incorrect Python package into the charm. `charmcraft` builds the charm using the LXD container with the appropriate Ubuntu image, so there is no such problem with `charmcraft`.
In this MP, change the integration test to call `charmcraft` instead of using `ops_test.
This merge proposal is being monitored by mergebot. Change the status to Approved to merge.