semvec/pypi-packages huggingface dataset:
hypermodern-python-example 0.1.0
The hypermodern Python example
License: MIT
Requires Python: >=3.9,<4.0
Keywords: hypermodern

[![Tests](https://github.com/paulrousset/hypermodern-python-example/workflows/Tests/badge.svg)](https://github.com/paulrousset/hypermodern-python-example/actions?workflow=Tests)
[![Codecov](https://codecov.io/gh/paulrousset/hypermodern-python-example/branch/master/graph/badge.svg)](https://codecov.io/gh/paulrousset/hypermodern-python-example)
[![PyPI](https://img.shields.io/pypi/v/hypermodern-python-example.svg)](https://pypi.org/project/hypermodern-python-example/)
[![Read the Docs](https://readthedocs.org/projects/hypermodern-python-example/badge/)](https://hypermodern-python-example.readthedocs.io/)

# hypermodern-python-example
Example of setup with hypermodern python tooling
pytest-pymysql-autorecord 0.1.0
Record PyMySQL queries and mock with the stored data.
License: MIT

# pytest-pymysql-autorecording

A pytest plugin for recording database query results and mocking with the stored data.

## Mocking with real database data

In principle, mocking database data is a good idea. But if your database is very complex, this may easily become tedious and may lack the richness of the real data.

Testing with real data leads to another problem, though: You might not want to grant your CI/CD pipeline on, say, GitHub, access to a database.

So this plugin offers a compromise. You still run tests against a real database, and you store the query results. The stored results can then be used by the CI/CD pipeline to mock the database queries.

## Using the plugin

Please refer to the [Quickstart Guide](https://saltastroops.github.io/pytest-pymysql-autorecord/quickstart.html) to find out how to use the plugin.