Pytest-dbfixtures

Latest version: v1.0.0

Safety actively analyzes 682532 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 3 of 7

0.10.0

------

- fix W503 pep8 errors, that appeared after new pylama got released
- update to be able to use pytest-dbfixtures with pymongo 3
- ability to properly use also beta versions of postgresql releases. (previously only stable versions were targeted)

0.9.0

-----

- add ability to set custom location for logs (might be useful for analysing logs from tests)
- added postgresql 9.4 to supported versions.

0.8.2

-----

- Use port number in default RabbitMQ node name.

This allows using just the port='?' argument to rabbitmq_proc to run multiple
independent RabbitMQ instances for use with xdist to parallelize tests on a
single machine.

- Old versions of Redis notification

displays a message about old version of redis

0.8.1

-----

- Feature: random ports selection
Adds a possibility of passing '?' in port= argument of process fixtures.
- Removes 'port' from db fixtures
- Fixes postgres missing host - previously using config.postgresql.unixsocketdir

0.7.0

-----

- redisdb fixture allows to specify client connection class
- redisdb fixture uses now StrictRedis by default (backward incompatible)

0.6.0

-----

- replaced *MySQLdb* with it's fork *mysqlclient* - compatibility with python3
- renamed mysqldb fixture to mysql to keep it consistent with other client fixtures.
- replaced *pika* with python 3 compatible rabbitpy
- removed deprecated mysqldb_session/mysql_session
- bugfix of rabbitmq fixture: cast rabbitmq queues and exchanges to str due to pamq having problems
- internal changes: removed GentleKillingExecutor as mirakuru already implements same functionality

Page 3 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.