automatic import of python-pytest-mock-resources

1 files changed, 643 insertions, 0 deletions

diff --git a/python-pytest-mock-resources.spec b/python-pytest-mock-resources.spec
new file mode 100644
index 0000000..28ff6bf
--- /dev/null
+++ b/python-pytest-mock-resources.spec
@@ -0,0 +1,643 @@
+%global _empty_manifest_terminate_build 0
+Name:		python-pytest-mock-resources
+Version:	2.6.11
+Release:	1
+Summary:	A pytest plugin for easily instantiating reproducible mock resources.
+License:	MIT
+URL:		https://github.com/schireson/pytest-mock-resources
+Source0:	https://mirrors.nju.edu.cn/pypi/web/packages/6d/f1/edaa24d0ee5259d6dc3e54a0d39845fa633126e3157acf7d0e9ae93fa0d6/pytest_mock_resources-2.6.11.tar.gz
+BuildArch:	noarch
+
+Requires:	python3-pytest
+Requires:	python3-sqlalchemy
+Requires:	python3-psycopg2
+Requires:	python3-psycopg2-binary
+Requires:	python3-asyncpg
+Requires:	python3-moto
+Requires:	python3-boto3
+Requires:	python3-sqlparse
+Requires:	python3-pymongo
+Requires:	python3-redis
+Requires:	python3-pymysql
+Requires:	python3-filelock
+Requires:	python3-on-whales
+
+%description
+![CircleCI](https://img.shields.io/circleci/build/gh/schireson/pytest-mock-resources/master)
+[![codecov](https://codecov.io/gh/schireson/pytest-mock-resources/branch/master/graph/badge.svg)](https://codecov.io/gh/schireson/pytest-mock-resources)
+[![Documentation
+Status](https://readthedocs.org/projects/pytest-mock-resources/badge/?version=latest)](https://pytest-mock-resources.readthedocs.io/en/latest/?badge=latest)
+
+## Introduction
+
+Code which depends on external resources such a databases (postgres, redshift, etc) can be difficult
+to write automated tests for. Conventional wisdom might be to mock or stub out the actual database
+calls and assert that the code works correctly before/after the calls.
+
+However take the following, _simple_ example:
+
+```python
+def serialize(users):
+    return [
+        {
+            'user': user.serialize(),
+            'address': user.address.serialize(),
+            'purchases': [p.serialize() for p in user.purchases],
+        }
+        for user in users
+    ]
+
+def view_function(session):
+    users = session.query(User).join(Address).options(selectinload(User.purchases)).all()
+    return serialize(users)
+```
+
+Sure, you can test `serialize`, but whether the actual **query** did the correct thing _truly_
+requires that you execute the query.
+
+## The Pitch
+
+Having tests depend upon a **real** postgres instance running somewhere is a pain, very fragile, and
+prone to issues across machines and test failures.
+
+Therefore `pytest-mock-resources` (primarily) works by managing the lifecycle of docker containers
+and providing access to them inside your tests.
+
+As such, this package makes 2 primary assumptions:
+
+- You're using `pytest` (hopefully that's appropriate, given the package name)
+- For many resources, `docker` is required to be available and running (or accessible through remote
+  docker).
+
+If you aren't familiar with Pytest Fixtures, you can read up on them in the [Pytest
+documentation](https://docs.pytest.org/en/latest/fixture.html).
+
+In the above example, your test file could look something like
+
+```python
+from pytest_mock_resources import create_postgres_fixture
+from models import ModelBase
+
+pg = create_postgres_fixture(ModelBase, session=True)
+
+def test_view_function_empty_db(pg):
+  response = view_function(pg)
+  assert response == ...
+
+def test_view_function_user_without_purchases(pg):
+  pg.add(User(...))
+  pg.flush()
+
+  response = view_function(pg)
+  assert response == ...
+
+def test_view_function_user_with_purchases(pg):
+  pg.add(User(..., purchases=[Purchase(...)]))
+  pg.flush()
+
+  response = view_function(pg)
+  assert response == ...
+```
+
+## Existing Resources (many more possible)
+
+- SQLite
+
+  ```python
+  from pytest_mock_resources import create_sqlite_fixture
+  ```
+
+- Postgres
+
+  ```python
+  from pytest_mock_resources import create_postgres_fixture
+  ```
+
+- Redshift
+
+  **note** Uses postgres under the hood, but the fixture tries to support as much redshift
+  functionality as possible (including redshift's `COPY`/`UNLOAD` commands).
+
+  ```python
+  from pytest_mock_resources import create_redshift_fixture
+  ```
+
+- Mongo
+
+  ```python
+  from pytest_mock_resources import create_mongo_fixture
+  ```
+
+- Redis
+
+  ```python
+  from pytest_mock_resources import create_redis_fixture
+  ```
+
+- MySQL
+
+  ```python
+  from pytest_mock_resources import create_mysql_fixture
+  ```
+
+- Moto
+
+  ```python
+  from pytest_mock_resources import create_moto_fixture
+  ```
+
+## Features
+
+General features include:
+
+- Support for "actions" which pre-populate the resource you're mocking before the test
+- [Async fixtures](https://pytest-mock-resources.readthedocs.io/en/latest/async.html)
+- Custom configuration for container/resource startup
+
+## Installation
+
+```bash
+# Basic fixture support i.e. SQLite
+pip install "pytest-mock-resources"
+
+# General, docker-based fixture support
+pip install "pytest-mock-resources[docker]"
+
+# Mongo fixture support, installs `pymongo`
+pip install "pytest-mock-resources[mongo]"
+
+# Moto fixture support, installs non-driver extras specific to moto support
+pip install "pytest-mock-resources[moto]"
+
+# Redis fixture support, Installs `redis` client
+pip install "pytest-mock-resources[redis]"
+
+# Redshift fixture support, installs non-driver extras specific to redshift support
+pip install "pytest-mock-resources[redshift]"
+```
+
+Additionally there are number of **convenience** extras currently provided
+for installing drivers/clients of specific features. However in most cases,
+you **should** already be installing the driver/client used for that fixture
+as as first-party dependency of your project.
+
+As such, we recommend against using these extras, and instead explcitly depending
+on the package in question in your own project's 1st party dependencies.
+
+```bash
+# Installs psycopg2/psycopg2-binary driver
+pip install "pytest-mock-resources[postgres-binary]"
+pip install "pytest-mock-resources[postgres]"
+
+# Installs asyncpg driver
+pip install "pytest-mock-resources[postgres-async]"
+
+# Installs pymysql driver
+pip install "pytest-mock-resources[mysql]"
+```
+
+## Possible Future Resources
+
+- Rabbit Broker
+- AWS Presto
+
+Feel free to file an [issue](https://github.com/schireson/pytest-mock-resources/issues) if you find
+any bugs or want to start a conversation around a mock resource you want implemented!
+
+## Python 2
+
+Releases in the 1.x series were supportive of python 2. However starting from 2.0.0, support for
+python 2 was dropped. We may accept bugfix PRs for the 1.x series, however new development and
+features will not be backported.
+
+
+%package -n python3-pytest-mock-resources
+Summary:	A pytest plugin for easily instantiating reproducible mock resources.
+Provides:	python-pytest-mock-resources
+BuildRequires:	python3-devel
+BuildRequires:	python3-setuptools
+BuildRequires:	python3-pip
+%description -n python3-pytest-mock-resources
+![CircleCI](https://img.shields.io/circleci/build/gh/schireson/pytest-mock-resources/master)
+[![codecov](https://codecov.io/gh/schireson/pytest-mock-resources/branch/master/graph/badge.svg)](https://codecov.io/gh/schireson/pytest-mock-resources)
+[![Documentation
+Status](https://readthedocs.org/projects/pytest-mock-resources/badge/?version=latest)](https://pytest-mock-resources.readthedocs.io/en/latest/?badge=latest)
+
+## Introduction
+
+Code which depends on external resources such a databases (postgres, redshift, etc) can be difficult
+to write automated tests for. Conventional wisdom might be to mock or stub out the actual database
+calls and assert that the code works correctly before/after the calls.
+
+However take the following, _simple_ example:
+
+```python
+def serialize(users):
+    return [
+        {
+            'user': user.serialize(),
+            'address': user.address.serialize(),
+            'purchases': [p.serialize() for p in user.purchases],
+        }
+        for user in users
+    ]
+
+def view_function(session):
+    users = session.query(User).join(Address).options(selectinload(User.purchases)).all()
+    return serialize(users)
+```
+
+Sure, you can test `serialize`, but whether the actual **query** did the correct thing _truly_
+requires that you execute the query.
+
+## The Pitch
+
+Having tests depend upon a **real** postgres instance running somewhere is a pain, very fragile, and
+prone to issues across machines and test failures.
+
+Therefore `pytest-mock-resources` (primarily) works by managing the lifecycle of docker containers
+and providing access to them inside your tests.
+
+As such, this package makes 2 primary assumptions:
+
+- You're using `pytest` (hopefully that's appropriate, given the package name)
+- For many resources, `docker` is required to be available and running (or accessible through remote
+  docker).
+
+If you aren't familiar with Pytest Fixtures, you can read up on them in the [Pytest
+documentation](https://docs.pytest.org/en/latest/fixture.html).
+
+In the above example, your test file could look something like
+
+```python
+from pytest_mock_resources import create_postgres_fixture
+from models import ModelBase
+
+pg = create_postgres_fixture(ModelBase, session=True)
+
+def test_view_function_empty_db(pg):
+  response = view_function(pg)
+  assert response == ...
+
+def test_view_function_user_without_purchases(pg):
+  pg.add(User(...))
+  pg.flush()
+
+  response = view_function(pg)
+  assert response == ...
+
+def test_view_function_user_with_purchases(pg):
+  pg.add(User(..., purchases=[Purchase(...)]))
+  pg.flush()
+
+  response = view_function(pg)
+  assert response == ...
+```
+
+## Existing Resources (many more possible)
+
+- SQLite
+
+  ```python
+  from pytest_mock_resources import create_sqlite_fixture
+  ```
+
+- Postgres
+
+  ```python
+  from pytest_mock_resources import create_postgres_fixture
+  ```
+
+- Redshift
+
+  **note** Uses postgres under the hood, but the fixture tries to support as much redshift
+  functionality as possible (including redshift's `COPY`/`UNLOAD` commands).
+
+  ```python
+  from pytest_mock_resources import create_redshift_fixture
+  ```
+
+- Mongo
+
+  ```python
+  from pytest_mock_resources import create_mongo_fixture
+  ```
+
+- Redis
+
+  ```python
+  from pytest_mock_resources import create_redis_fixture
+  ```
+
+- MySQL
+
+  ```python
+  from pytest_mock_resources import create_mysql_fixture
+  ```
+
+- Moto
+
+  ```python
+  from pytest_mock_resources import create_moto_fixture
+  ```
+
+## Features
+
+General features include:
+
+- Support for "actions" which pre-populate the resource you're mocking before the test
+- [Async fixtures](https://pytest-mock-resources.readthedocs.io/en/latest/async.html)
+- Custom configuration for container/resource startup
+
+## Installation
+
+```bash
+# Basic fixture support i.e. SQLite
+pip install "pytest-mock-resources"
+
+# General, docker-based fixture support
+pip install "pytest-mock-resources[docker]"
+
+# Mongo fixture support, installs `pymongo`
+pip install "pytest-mock-resources[mongo]"
+
+# Moto fixture support, installs non-driver extras specific to moto support
+pip install "pytest-mock-resources[moto]"
+
+# Redis fixture support, Installs `redis` client
+pip install "pytest-mock-resources[redis]"
+
+# Redshift fixture support, installs non-driver extras specific to redshift support
+pip install "pytest-mock-resources[redshift]"
+```
+
+Additionally there are number of **convenience** extras currently provided
+for installing drivers/clients of specific features. However in most cases,
+you **should** already be installing the driver/client used for that fixture
+as as first-party dependency of your project.
+
+As such, we recommend against using these extras, and instead explcitly depending
+on the package in question in your own project's 1st party dependencies.
+
+```bash
+# Installs psycopg2/psycopg2-binary driver
+pip install "pytest-mock-resources[postgres-binary]"
+pip install "pytest-mock-resources[postgres]"
+
+# Installs asyncpg driver
+pip install "pytest-mock-resources[postgres-async]"
+
+# Installs pymysql driver
+pip install "pytest-mock-resources[mysql]"
+```
+
+## Possible Future Resources
+
+- Rabbit Broker
+- AWS Presto
+
+Feel free to file an [issue](https://github.com/schireson/pytest-mock-resources/issues) if you find
+any bugs or want to start a conversation around a mock resource you want implemented!
+
+## Python 2
+
+Releases in the 1.x series were supportive of python 2. However starting from 2.0.0, support for
+python 2 was dropped. We may accept bugfix PRs for the 1.x series, however new development and
+features will not be backported.
+
+
+%package help
+Summary:	Development documents and examples for pytest-mock-resources
+Provides:	python3-pytest-mock-resources-doc
+%description help
+![CircleCI](https://img.shields.io/circleci/build/gh/schireson/pytest-mock-resources/master)
+[![codecov](https://codecov.io/gh/schireson/pytest-mock-resources/branch/master/graph/badge.svg)](https://codecov.io/gh/schireson/pytest-mock-resources)
+[![Documentation
+Status](https://readthedocs.org/projects/pytest-mock-resources/badge/?version=latest)](https://pytest-mock-resources.readthedocs.io/en/latest/?badge=latest)
+
+## Introduction
+
+Code which depends on external resources such a databases (postgres, redshift, etc) can be difficult
+to write automated tests for. Conventional wisdom might be to mock or stub out the actual database
+calls and assert that the code works correctly before/after the calls.
+
+However take the following, _simple_ example:
+
+```python
+def serialize(users):
+    return [
+        {
+            'user': user.serialize(),
+            'address': user.address.serialize(),
+            'purchases': [p.serialize() for p in user.purchases],
+        }
+        for user in users
+    ]
+
+def view_function(session):
+    users = session.query(User).join(Address).options(selectinload(User.purchases)).all()
+    return serialize(users)
+```
+
+Sure, you can test `serialize`, but whether the actual **query** did the correct thing _truly_
+requires that you execute the query.
+
+## The Pitch
+
+Having tests depend upon a **real** postgres instance running somewhere is a pain, very fragile, and
+prone to issues across machines and test failures.
+
+Therefore `pytest-mock-resources` (primarily) works by managing the lifecycle of docker containers
+and providing access to them inside your tests.
+
+As such, this package makes 2 primary assumptions:
+
+- You're using `pytest` (hopefully that's appropriate, given the package name)
+- For many resources, `docker` is required to be available and running (or accessible through remote
+  docker).
+
+If you aren't familiar with Pytest Fixtures, you can read up on them in the [Pytest
+documentation](https://docs.pytest.org/en/latest/fixture.html).
+
+In the above example, your test file could look something like
+
+```python
+from pytest_mock_resources import create_postgres_fixture
+from models import ModelBase
+
+pg = create_postgres_fixture(ModelBase, session=True)
+
+def test_view_function_empty_db(pg):
+  response = view_function(pg)
+  assert response == ...
+
+def test_view_function_user_without_purchases(pg):
+  pg.add(User(...))
+  pg.flush()
+
+  response = view_function(pg)
+  assert response == ...
+
+def test_view_function_user_with_purchases(pg):
+  pg.add(User(..., purchases=[Purchase(...)]))
+  pg.flush()
+
+  response = view_function(pg)
+  assert response == ...
+```
+
+## Existing Resources (many more possible)
+
+- SQLite
+
+  ```python
+  from pytest_mock_resources import create_sqlite_fixture
+  ```
+
+- Postgres
+
+  ```python
+  from pytest_mock_resources import create_postgres_fixture
+  ```
+
+- Redshift
+
+  **note** Uses postgres under the hood, but the fixture tries to support as much redshift
+  functionality as possible (including redshift's `COPY`/`UNLOAD` commands).
+
+  ```python
+  from pytest_mock_resources import create_redshift_fixture
+  ```
+
+- Mongo
+
+  ```python
+  from pytest_mock_resources import create_mongo_fixture
+  ```
+
+- Redis
+
+  ```python
+  from pytest_mock_resources import create_redis_fixture
+  ```
+
+- MySQL
+
+  ```python
+  from pytest_mock_resources import create_mysql_fixture
+  ```
+
+- Moto
+
+  ```python
+  from pytest_mock_resources import create_moto_fixture
+  ```
+
+## Features
+
+General features include:
+
+- Support for "actions" which pre-populate the resource you're mocking before the test
+- [Async fixtures](https://pytest-mock-resources.readthedocs.io/en/latest/async.html)
+- Custom configuration for container/resource startup
+
+## Installation
+
+```bash
+# Basic fixture support i.e. SQLite
+pip install "pytest-mock-resources"
+
+# General, docker-based fixture support
+pip install "pytest-mock-resources[docker]"
+
+# Mongo fixture support, installs `pymongo`
+pip install "pytest-mock-resources[mongo]"
+
+# Moto fixture support, installs non-driver extras specific to moto support
+pip install "pytest-mock-resources[moto]"
+
+# Redis fixture support, Installs `redis` client
+pip install "pytest-mock-resources[redis]"
+
+# Redshift fixture support, installs non-driver extras specific to redshift support
+pip install "pytest-mock-resources[redshift]"
+```
+
+Additionally there are number of **convenience** extras currently provided
+for installing drivers/clients of specific features. However in most cases,
+you **should** already be installing the driver/client used for that fixture
+as as first-party dependency of your project.
+
+As such, we recommend against using these extras, and instead explcitly depending
+on the package in question in your own project's 1st party dependencies.
+
+```bash
+# Installs psycopg2/psycopg2-binary driver
+pip install "pytest-mock-resources[postgres-binary]"
+pip install "pytest-mock-resources[postgres]"
+
+# Installs asyncpg driver
+pip install "pytest-mock-resources[postgres-async]"
+
+# Installs pymysql driver
+pip install "pytest-mock-resources[mysql]"
+```
+
+## Possible Future Resources
+
+- Rabbit Broker
+- AWS Presto
+
+Feel free to file an [issue](https://github.com/schireson/pytest-mock-resources/issues) if you find
+any bugs or want to start a conversation around a mock resource you want implemented!
+
+## Python 2
+
+Releases in the 1.x series were supportive of python 2. However starting from 2.0.0, support for
+python 2 was dropped. We may accept bugfix PRs for the 1.x series, however new development and
+features will not be backported.
+
+
+%prep
+%autosetup -n pytest-mock-resources-2.6.11
+
+%build
+%py3_build
+
+%install
+%py3_install
+install -d -m755 %{buildroot}/%{_pkgdocdir}
+if [ -d doc ]; then cp -arf doc %{buildroot}/%{_pkgdocdir}; fi
+if [ -d docs ]; then cp -arf docs %{buildroot}/%{_pkgdocdir}; fi
+if [ -d example ]; then cp -arf example %{buildroot}/%{_pkgdocdir}; fi
+if [ -d examples ]; then cp -arf examples %{buildroot}/%{_pkgdocdir}; fi
+pushd %{buildroot}
+if [ -d usr/lib ]; then
+	find usr/lib -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/lib64 ]; then
+	find usr/lib64 -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/bin ]; then
+	find usr/bin -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+if [ -d usr/sbin ]; then
+	find usr/sbin -type f -printf "/%h/%f\n" >> filelist.lst
+fi
+touch doclist.lst
+if [ -d usr/share/man ]; then
+	find usr/share/man -type f -printf "/%h/%f.gz\n" >> doclist.lst
+fi
+popd
+mv %{buildroot}/filelist.lst .
+mv %{buildroot}/doclist.lst .
+
+%files -n python3-pytest-mock-resources -f filelist.lst
+%dir %{python3_sitelib}/*
+
+%files help -f doclist.lst
+%{_docdir}/*
+
+%changelog
+* Tue Apr 11 2023 Python_Bot <Python_Bot@openeuler.org> - 2.6.11-1
+- Package Spec generated