delta/python-packages/sqlalchemy.git/README.unittests.rst, branch rel_1_1

commit 1b774808c926665047bf353222ecd191679a95d1

2018-12-31T02:23:37+00:00

Author: Lele Gaifax 
Date:   Tue Dec 25 12:35:41 2018 +0100

    Consistently use "PostgreSQL", fixing also a few doc glitches

commit 0e382aaee4427193926f0dc10ad29056bc12c85e
Author: Lele Gaifax 
Date:   Tue Dec 25 12:08:49 2018 +0100

    Remove duplicated words

Change-Id: Iaa586b9412f46a50fe6ff3bbb92e07d6cb1905c8
(cherry picked from commit c0f9708fde39175c8695fdd87873464f516fdf98)
(cherry picked from commit 7ec092063a7defe2b60d8f01b2eb3cda9dd28c90)

- rework the unittests README which was very out of date

2017-08-19T18:06:40+00:00

Change-Id: Id9bda43ea493a8d493be5ecb19da16a91a298f9d
(cherry picked from commit 31491a6acca68d6708e3e8ba1bc9ea842a54d5fe)

spelling: Postgresql -> PostgreSQL

2016-10-08T17:42:50+00:00

- Added support for the :class:`postgresql.JSONB` datatype when

2015-02-01T00:04:54+00:00

using psycopg2 2.5.4 or greater, which features native conversion
of JSONB data so that SQLAlchemy's converters must be disabled;
additionally, the newly added psycopg2 extension
``extras.register_default_jsonb`` is used to establish a JSON
deserializer passed to the dialect via the ``json_deserializer``
argument.  Also repaired the Postgresql integration tests which
weren't actually round-tripping the JSONB type as opposed to the
JSON type.  Pull request courtesy Mateusz Susik.

- Repaired the use of the "array_oid" flag when registering the
HSTORE type with older psycopg2 versions < 2.4.3, which does not
support this flag, as well as use of the native json serializer
hook "register_default_json" with user-defined ``json_deserializer``
on psycopg2 versions < 2.5, which does not include native json.

- memusage is fine for parallel

2014-08-08T17:48:27+00:00

- add support for tags, including include/exclude support.

2014-07-27T22:46:20+00:00

simplify tox again now that we can exclude tests more easily

- reorganize tox options

2014-07-27T01:18:19+00:00

Add note on PostgreSQL config for test runs

2014-05-15T21:02:59+00:00

Several tests on PostgreSQL depend on English-language text search
config being the default in the test DB. This adds a note about that.

- cx_oracle test for "unicode returns" needs to be cx_oracle only,

2014-03-06T16:57:54+00:00

and also will fail on py3k.
- enhance exclusions so that a requirement attribute can be passed
to fails_if/skip_if.
- fix coverage docs to mention pytest.

- Support has been added for pytest to run tests. This runner

2014-03-03T20:55:17+00:00

is currently being supported in addition to nose, and will likely
be preferred to nose going forward.   The nose plugin system used
by SQLAlchemy has been split out so that it works under pytest as
well.  There are no plans to drop support for nose at the moment
and we hope that the test suite itself can continue to remain as
agnostic of testing platform as possible.  See the file
README.unittests.rst for updated information on running tests
with pytest.

The test plugin system has also been enhanced to support running
tests against mutiple database URLs at once, by specifying the ``--db``
and/or ``--dburi`` flags multiple times.  This does not run the entire test
suite for each database, but instead allows test cases that are specific
to certain backends make use of that backend as the test is run.
When using pytest as the test runner, the system will also run
specific test suites multiple times, once for each database, particularly
those tests within the "dialect suite".   The plan is that the enhanced
system will also be used by Alembic, and allow Alembic to run
migration operation tests against multiple backends in one run, including
third-party backends not included within Alembic itself.
Third party dialects and extensions are also encouraged to standardize
on SQLAlchemy's test suite as a basis; see the file README.dialects.rst
for background on building out from SQLAlchemy's test platform.