summaryrefslogtreecommitdiff
path: root/README.unittests.rst
Commit message (Collapse)AuthorAgeFilesLines
* Rename py.test to pytestGord Thompson2020-04-161-17/+17
| | | | Change-Id: I431e1ef41e26d490343204a75a5c097768749768
* Deprecate plain string in execute and introduce `exec_driver_sql`Federico Caselli2020-03-211-1/+1
| | | | | | | | | | | | | | | Execution of literal sql string is deprecated in the :meth:`.Connection.execute` and a warning is raised when used stating that it will be coerced to :func:`.text` in a future release. To execute a raw sql string the new connection method :meth:`.Connection.exec_driver_sql` was added, that will retain the previous behavior, passing the string to the DBAPI driver unchanged. Usage of scalar or tuple positional parameters in :meth:`.Connection.execute` is also deprecated. Fixes: #4848 Fixes: #5178 Change-Id: I2830181054327996d594f7f0d59c157d477c3aa9
* Support inspection of computed columnFederico Caselli2020-03-151-1/+1
| | | | | | | | | | | | | | | | | | | Added support for reflection of "computed" columns, which are now returned as part of the structure returned by :meth:`.Inspector.get_columns`. When reflecting full :class:`.Table` objects, computed columns will be represented using the :class:`.Computed` construct. Also improve the documentation in :meth:`Inspector.get_columns`, correctly listing all the returned keys. Fixes: #5063 Fixes: #4051 Closes: #5064 Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/5064 Pull-request-sha: ba00fc321ce468f8885aad23b3dd33c789e50fbe Change-Id: I789986554fc8ac7f084270474d0b2c12046b1cc2
* Add docker commands to README.unittestsFederico Caselli2020-03-041-1/+67
| | | | | | | | Closes: #5116 Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/5116 Pull-request-sha: e70ad70426de03982c3abb78eb7b8292e86c3950 Change-Id: If9ef93312d8ce78908a76ea84cb95f3068ffb306
* Improve two phase transaction requirement detection for PGFederico Caselli2019-12-281-0/+6
| | | | | | | | | | | | | Improved detection of two phase transactions requirement for the PostgreSQL database by testing that max_prepared_transactions is set to a value greater than 0. Pull request courtesy Federico Caselli. Fixes: #5057 Closes: #5059 Pull-request: https://github.com/sqlalchemy/sqlalchemy/pull/5059 Pull-request-sha: c30c3b1a5216d281db84f9fa48466edaf7a26d1e Change-Id: I4360f62eacdf1173172ee24cd05a68e9a448290c
* Fix charset= in README.unittests.rst for MySQLGord Thompson2019-11-171-3/+3
|
* Remove python setup.py test; fix SQL Server URLMike Bayer2019-10-281-30/+50
| | | | | | | | general README.unittest.rst edits Fixes: #4789 Fixes: #4900 Change-Id: Ifddd3bfd1e6a4d24d3b0a3e1702e04e66a42a4dd
* commit 1b774808c926665047bf353222ecd191679a95d1Lele Gaifax2018-12-301-3/+3
| | | | | | | | | | | | | | | Author: Lele Gaifax <lele@metapensiero.it> Date: Tue Dec 25 12:35:41 2018 +0100 Consistently use "PostgreSQL", fixing also a few doc glitches commit 0e382aaee4427193926f0dc10ad29056bc12c85e Author: Lele Gaifax <lele@metapensiero.it> Date: Tue Dec 25 12:08:49 2018 +0100 Remove duplicated words Change-Id: Iaa586b9412f46a50fe6ff3bbb92e07d6cb1905c8
* - rework the unittests README which was very out of dateMike Bayer2017-08-191-233/+104
| | | | Change-Id: Id9bda43ea493a8d493be5ecb19da16a91a298f9d
* spelling: Postgresql -> PostgreSQLVille Skyttä2016-10-081-3/+3
|
* - Added support for the :class:`postgresql.JSONB` datatype whenMike Bayer2015-01-311-0/+12
| | | | | | | | | | | | | | | | | 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 parallelMike Bayer2014-08-081-1/+1
|
* - add support for tags, including include/exclude support.Mike Bayer2014-07-271-7/+3
| | | | simplify tox again now that we can exclude tests more easily
* - reorganize tox optionsMike Bayer2014-07-261-23/+27
|
* Add note on PostgreSQL config for test runsGunnlaugur Þór Briem2014-05-151-0/+6
| | | | | 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,Mike Bayer2014-03-061-2/+3
| | | | | | | 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 runnerMike Bayer2014-03-031-53/+119
| | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* README.unittests.rst: Add blurb about toxpr/49Marc Abramowitz2013-11-251-0/+39
|
* - replace most explicitly-named test objects called "Mock..." withMike Bayer2013-06-301-1/+7
| | | | | | | | | | | | actual mock objects from the mock library. I'd like to use mock for new tests so we might as well use it in obvious places. - use unittest.mock in py3.3 - changelog - add a note to README.unittests - add tests_require in setup.py - have tests import from sqlalchemy.testing.mock - apply usage of mock to one of the event tests. we can be using this approach all over the place.
* this is an RST nowMike Bayer2012-10-101-0/+210
View Lorry Controller Status