Skip to main content

MySQL process and client fixtures for pytest

Project description

https://raw.githubusercontent.com/ClearcodeHQ/pytest-mysql/master/logo.png

pytest-mysql

Latest PyPI version Wheel Status Supported Python Versions License

What is this?

This is a pytest plugin, that enables you to test your code that relies on a running MySQL Database. It allows you to specify fixtures for MySQL process and client.

How to use

Plugin contains two fixtures

  • mysql - it’s a client fixture that has functional scope. After each test drops test database from MySQL ensuring repeatability.

  • mysql_proc - session scoped fixture, that starts MySQL instance at it’s first use and stops at the end of the tests.

Simply include one of these fixtures into your tests fixture list.

You can also create additional mysql client and process fixtures if you’d need to:

from pytest_mysql import factories

mysql_my_proc = factories.mysql_proc(
    port=None, logsdir='/tmp')
mysql_my = factories.mysql('mysql_my_proc')

Configuration

You can define your settings in three ways, it’s fixture factory argument, command line option and pytest.ini configuration option. You can pick which you prefer, but remember that these settings are handled in the following order:

  • Fixture factory argument

  • Command line option

  • Configuration option in your pytest.ini file

. list-table:: Configuration options
header-rows:

1

    • MySQL/MariaDB option

    • Fixture factory argument

    • Command line option

    • pytest.ini option

    • Noop process fixture

    • Default

    • Path to executable

    • mysqld_exec

    • –mysql-mysqld

    • mysql_mysqld

    • mysqld

    • Path to safe executable

    • mysqld_safe

    • –mysql-mysqld-safe

    • mysql_mysqld_safe

    • mysqld_safe

    • Path to mysql_install_db for legacy installations

    • install_db

    • –mysql-install-db

    • mysql_install_db

    • mysql_install_db

    • Path to Admin executable

    • admin_executable

    • –mysql-admin

    • mysql_admin

    • mysqladmin

    • Database hostname

    • host

    • –mysql-host

    • mysql_host

    • localhost

    • Database port

    • port

    • –mysql-port

    • mysql_port

    • random

    • MySQL user to work with

    • user

    • –mysql-user

    • mysql_user

    • root

    • User’s password

    • passwd

    • –mysql-passwd

    • mysql_passwd

    • Test database name

    • dbname

    • –mysql-dbname

    • mysqldbname

    • test

    • Starting parameters

    • params

    • –mysql-params

    • mysql_params

    • Log directory location [DEPRECATED]

    • logsdir

    • –mysql-logsdir

    • mysql_logsdir

    • $TMPDIR

Example usage:

  • pass it as an argument in your own fixture

    mysql_proc = factories.mysql_proc(
        port=8888)
  • use --mysql-port command line option when you run your tests

    py.test tests --mysql-port=8888
  • specify your port as mysql_port in your pytest.ini file.

    To do so, put a line like the following under the [pytest] section of your pytest.ini:

    [pytest]
    mysql_port = 8888

Examples

Populating database for tests

With SQLAlchemy

This example shows how to populate database and create an SQLAlchemy’s ORM connection:

Sample below is simplified session fixture from pyramid_fullauth tests:

from sqlalchemy import create_engine
from sqlalchemy.orm import scoped_session, sessionmaker
from sqlalchemy.pool import NullPool
from zope.sqlalchemy import register


@pytest.fixture
def db_session(mysql):
    """Session for SQLAlchemy."""
    from pyramid_fullauth.models import Base  # pylint:disable=import-outside-toplevel

    # assumes setting, these can be obtained from pytest-mysql config or mysql_proc
    connection = f'mysql+mysqldb://root:@127.0.0.1:3307/tests?charset=utf8'

    engine = create_engine(connection, echo=False, poolclass=NullPool)
    pyramid_basemodel.Session = scoped_session(sessionmaker(extension=ZopeTransactionExtension()))
    pyramid_basemodel.bind_engine(
        engine, pyramid_basemodel.Session, should_create=True, should_drop=True)

    yield pyramid_basemodel.Session

    transaction.commit()
    Base.metadata.drop_all(engine)


@pytest.fixture
def user(db_session):
    """Test user fixture."""
    from pyramid_fullauth.models import User
    from tests.tools import DEFAULT_USER

    new_user = User(**DEFAULT_USER)
    db_session.add(new_user)
    transaction.commit()
    return new_user


def test_remove_last_admin(db_session, user):
    """
    Sample test checks internal login, but shows usage in tests with SQLAlchemy
    """
    user = db_session.merge(user)
    user.is_admin = True
    transaction.commit()
    user = db_session.merge(user)

    with pytest.raises(AttributeError):
        user.is_admin = False

Connecting to MySQL/MariaDB (in a docker)

To connect to a docker run postgresql and run test on it, use noproc fixtures.

docker run --name some-db -e MYSQL_ALLOW_EMPTY_PASSWORD=yes -d mysql --expose 3306
docker run --name some-db -e MARIADB_ALLOW_EMPTY_PASSWORD=yes -d mariadb --expose 3306

This will start postgresql in a docker container, however using a postgresql installed locally is not much different.

In tests, make sure that all your tests are using mysql_noproc fixture like that:

mysql_in_docker = factories.mysql_noproc()
mysql = factories.mysql("mysql_in_docker")


def test_mysql_docker(mysql):
    """Run test."""
    cur = mysql.cursor()
    cur.query("CREATE TABLE pet (name VARCHAR(20), owner VARCHAR(20), species VARCHAR(20), sex CHAR(1), birth DATE, death DATE);")
    mysql.commit()
    cur.close()

And run tests:

pytest --mysql-host=127.0.0.1

Running on Docker/as root

Unfortunately, running MySQL as root (thus by default on docker) is not possible. MySQL (and MariaDB as well) will not allow it.

USER nobody

This line should switch your docker process to run on user nobody. See this comment for example

Package resources

CHANGELOG

2.1.0

Feature

  • mysql_noproc fixture to connect to already running mysql server

  • raise more meaningful error when the test database already exists

Misc

  • rely on get_port functionality delivered by port_for

Deprecation

  • Deprecated mysql_logsdir ini configuration and –mysql-logsdir command option

  • Deprecated logs_prefix process fixture factory setting

Misc

  • Require minimum python 3.7

  • Migrate CI to Github Actions

2.0.3

  • [enhancement] Do not assume that mysql executables are in /usr/bin

2.0.2

  • [enhancement] Preemptively read data after each test in mysql client fixture. This will make test run if the test itself forgot to fetch queried data.

  • [enhnacement] Require at least mirakuru 2.3.0 - forced by changed stop method parameters change

2.0.1

  • [fix] Improved mysql version detection on osx

  • [build] extracted xdist into separate stage on travis

  • [build] have deployemt as separate stage on travis

2.0.0

  • [Enhancements] Add support for MySQL 5.7.6 and up with new configuration options. Legacy configuration supports older MySQL and MariaDB databases.

  • [breaking] mysql_exec ini option replaced with mysql_mysqld_safe

  • [breaking] –mysql-exec cmd option replaced with –mysql-mysqld-safe

  • [breaking] replaced mysql_init ini option with mysql_install_db

  • [breaking] replaced –mysql-init cmd option with –mysql-install-db

  • [breaking] added mysql_mysqld option and –mysql-mysqld cmd option

1.1.1

  • [enhancements] removed path.py dependency

1.1.0

  • [enhancement] change deprecated getfuncargvalaue to getfixturevalues, require at least pytest 3.0.0

1.0.0

  • [enhancements] create command line and pytest.ini configuration options for mysql’s log directory location

  • [enhancements] create command line and pytest.ini configuration options for mysql’s starting parametetrs

  • [enhancements] create command line and pytest.ini configuration options for mysql test database name

  • [enhancements] create command line and pytest.ini configuration options for mysql’s user password

  • [enhancements] create command line and pytest.ini configuration options for mysql user

  • [enhancements] create command line and pytest.ini configuration options for mysql host

  • [enhancements] create command line and pytest.ini configuration options for mysql port

  • [enhancements] create command line and pytest.ini configuration options for mysql’s init executable

  • [enhancements] create command line and pytest.ini configuration options for mysql’s admin executable

  • [enhancements] create command line and pytest.ini configuration options for mysql executable

  • [enhancements] create command line and pytest.ini configuration options for mysql logsdir

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

pytest-mysql-2.1.0.tar.gz (31.4 kB view details)

Uploaded Source

Built Distribution

pytest_mysql-2.1.0-py3-none-any.whl (30.9 kB view details)

Uploaded Python 3

File details

Details for the file pytest-mysql-2.1.0.tar.gz.

File metadata

  • Download URL: pytest-mysql-2.1.0.tar.gz
  • Upload date:
  • Size: 31.4 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/3.4.1 importlib_metadata/4.4.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.0 CPython/3.9.5

File hashes

Hashes for pytest-mysql-2.1.0.tar.gz
Algorithm Hash digest
SHA256 1919368486d0f1336b67facc845dcf6cf86973145e3b46e44816776f2dbbf0b0
MD5 00552e067a6390e2ec57b0512cfc0924
BLAKE2b-256 1d79de0b6926f11d6850d4c072dea4cdf9b7f51f8465225f9e119baf5c93b2ad

See more details on using hashes here.

File details

Details for the file pytest_mysql-2.1.0-py3-none-any.whl.

File metadata

  • Download URL: pytest_mysql-2.1.0-py3-none-any.whl
  • Upload date:
  • Size: 30.9 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/3.4.1 importlib_metadata/4.4.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.61.0 CPython/3.9.5

File hashes

Hashes for pytest_mysql-2.1.0-py3-none-any.whl
Algorithm Hash digest
SHA256 82df764ac1492ade1b954f8bc235dd822ab5a901c0eeef0bc818e6d7b6407b82
MD5 06a8ca297d35b796a15a64e8222d8688
BLAKE2b-256 3159a59405b63595e85b65cad562cdb8c685df93dacd15d7f624c9df6bfcbe0b

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page