Use unittest.mock instead of mock

The mock third party library was needed for mock support in py2
runtimes. Since we now only support py36 and later, we can use the
standard lib unittest.mock module instead.

Note that https://github.com/openstack/charms.openstack is used during tests
and he need `mock`, unfortunatelly it doesn't declare `mock` in its
requirements so it retrieve mock from other charm project (cross dependency).
So we depend on charms.openstack first and when
Ib1ed5b598a52375e29e247db9ab4786df5b6d142 will be merged then CI
will pass without errors.

Depends-On: Ib1ed5b598a52375e29e247db9ab4786df5b6d142
Change-Id: I1d7de2bd4d704ffc331fdeacea725e903890f296
This commit is contained in:
Hervé Beraud 2020-06-09 00:02:56 +02:00 committed by James Page
parent 0a03b2b36d
commit 1de27bc18f
7 changed files with 5 additions and 11 deletions

View File

@ -1,5 +1,4 @@
- project:
templates:
- python35-charm-jobs
- openstack-python3-ussuri-jobs
- openstack-cover-jobs

View File

@ -28,11 +28,6 @@ oslo.utils<=3.41.0;python_version<'3.6'
requests>=2.18.4
charms.reactive
# Newer mock seems to have some syntax which is newer than python3.5 (e.g.
# f'{something}'
mock>=1.2,<4.0.0; python_version < '3.6'
mock>=1.2; python_version >= '3.6'
nose>=1.3.7
coverage>=3.6
git+https://github.com/openstack/charms.openstack.git#egg=charms.openstack

View File

@ -1,6 +1,6 @@
# unit tests
import mock
from unittest import mock
import sys
sys.path.append('src')

View File

@ -1,4 +1,4 @@
import mock
from unittest import mock
from unittest.mock import patch
import lib.charm.vault as vault

View File

@ -1,4 +1,4 @@
import mock
from unittest import mock
from unittest.mock import patch
import hvac

View File

@ -1,4 +1,4 @@
import mock
from unittest import mock
from unittest.mock import patch, call
import charms.reactive

View File

@ -1,4 +1,4 @@
import mock
from unittest import mock
import unittest