summaryrefslogtreecommitdiff
path: root/lib/sqlalchemy/testing/plugin
Commit message (Collapse)AuthorAgeFilesLines
...
* - restate sort_tables in terms of a more fine grainedMike Bayer2015-01-011-11/+3
| | | | | | | | | | | | | sort_tables_and_constraints function. - The DDL generation system of :meth:`.MetaData.create_all` and :meth:`.Metadata.drop_all` has been enhanced to in most cases automatically handle the case of mutually dependent foreign key constraints; the need for the :paramref:`.ForeignKeyConstraint.use_alter` flag is greatly reduced. The system also works for constraints which aren't given a name up front; only in the case of DROP is a name required for at least one of the constraints involved in the cycle. fixes #3282
* - add a new option --force-write-profiles to rewrite profiles even if theyMike Bayer2014-11-251-1/+4
| | | | are passing
* - fix issue where nose Failure object comes into play hereMike Bayer2014-09-151-0/+2
|
* - remove some crufty old testing optionsMike Bayer2014-09-145-252/+81
| | | | | | | | - reestablish the "bootstrap" system of loading the test runners in testing/plugin; using the updated approach we just came up with for alembic. Coverage should be fixed now when running either py.test or nose. fixes #3196 - upgrade tox.ini and start using a .coveragerc file
* - A new style of warning can be emitted which will "filter" up toMike Bayer2014-08-311-3/+1
| | | | | | | | | N occurrences of a parameterized string. This allows parameterized warnings that can refer to their arguments to be delivered a fixed number of times until allowing Python warning filters to squelch them, and prevents memory from growing unbounded within Python's warning registries. fixes #3178
* - max failures 25Mike Bayer2014-08-161-0/+3
| | | | - guard against some potential pytest snarkiness
* - clean up provision and keep sqlite on memory DBs if thats what we start withMike Bayer2014-08-151-10/+7
|
* - modify how class state is tracked here as it seems like thingsMike Bayer2014-08-151-5/+6
| | | | are a little more crazy under xdist mode
* - repair against use hereMike Bayer2014-08-141-2/+3
|
* - public method name is get_enums()Mike Bayer2014-08-131-1/+9
| | | | | | | | | | | | | | - return a list of dicts like other methods do - don't combine 'schema' with 'name', leave them separate - support '*' argument so that we can retrieve cross-schema if needed - remove "conn" argument - use bound parameters for 'schema' in SQL - order by schema, name, label - adapt _load_enums changes to column reflection - changelog - module docs for get_enums() - add drop of enums to --dropfirst
* - repair test finding to not skip the test_suite testsMike Bayer2014-07-302-2/+1
|
* fix test ordering issuesMike Bayer2014-07-271-0/+2
|
* - remove print statementMike Bayer2014-07-271-3/+4
| | | | - ensure non-tests wont run
* - remove debugging assertionsMike Bayer2014-07-272-9/+5
| | | | - keep sqlite as memory even with parallel for now
* - add support for tags, including include/exclude support.Mike Bayer2014-07-273-29/+106
| | | | simplify tox again now that we can exclude tests more easily
* - scale up for mysql, sqliteMike Bayer2014-07-263-36/+172
|
* Merge branch 'master' into xdist_pocMike Bayer2014-07-261-26/+37
|\ | | | | | | | | Conflicts: lib/sqlalchemy/engine/url.py
| * - rework the exclusions system to have much better support for compoundMike Bayer2014-07-261-26/+37
| | | | | | | | rules, better message formatting
* | - use a template database for PG so extensions get created automaticallyMike Bayer2014-07-251-4/+7
| |
* | - proof of concept for parallel testingMike Bayer2014-07-253-0/+90
|/
* - apply pep8 formatting to sqlalchemy/sql, sqlalchemy/util, sqlalchemy/dialects,Brian Jarrett2014-07-203-82/+126
| | | | sqlalchemy/orm, sqlalchemy/event, sqlalchemy/testing
* - break up the <authors> copyright comment as part of a passMike Bayer2014-07-092-2/+4
| | | | to get all flake8 passing
* - support __only_on__ and __backend__ at the same timeMike Bayer2014-07-091-15/+19
|
* use importlib.machinery to load modules instead of imp under Python 3.3 and ↵Matt Chisholm2014-04-141-2/+7
| | | | | | greater part of #2830
* - fixes to multi-backend testsMike Bayer2014-03-273-13/+18
| | | | | - move the logic to determine "test id" into plugin_base - update callcounts
* fixes to get profiling tests working againMike Bayer2014-03-261-1/+7
|
* fixMike Bayer2014-03-241-1/+1
|
* - add some more rules to make sure all tests run if DBs are availableMike Bayer2014-03-241-1/+13
|
* - rename __multiple__ to __backend__, and apply __backend__ to a large ↵Mike Bayer2014-03-242-3/+7
| | | | | | number of tests. - move out logging tests from test_execute to test_logging
* unitttest has a SkipTest also but pytest doesn'tMike Bayer2014-03-111-6/+4
| | | | honor it unless nose is imported too...
* import testing needs to be here as we set .db on itMike Bayer2014-03-071-0/+1
|
* - cx_oracle test for "unicode returns" needs to be cx_oracle only,Mike Bayer2014-03-061-1/+0
| | | | | | | 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.
* - no unitest.SkipTest in 2.6...argggggMike Bayer2014-03-041-1/+9
|
* fix the profiling ids hereMike Bayer2014-03-031-1/+3
|
* - Support has been added for pytest to run tests. This runnerMike Bayer2014-03-033-412/+578
| | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* - happy new yearMike Bayer2014-01-051-1/+1
|
* - enhance the exclusions system to support database versions within the ↵Mike Bayer2013-12-171-6/+9
| | | | __only_on__ attribute
* - add copyright to source files missing itMike Bayer2013-10-261-0/+6
|
* - A large refactoring of the ``sqlalchemy.sql`` package has reorganizedMike Bayer2013-08-121-0/+2
| | | | | | | | | | | | | | | | | | | | | | the import structure of many core modules. ``sqlalchemy.schema`` and ``sqlalchemy.types`` remain in the top-level package, but are now just lists of names that pull from within ``sqlalchemy.sql``. Their implementations are now broken out among ``sqlalchemy.sql.type_api``, ``sqlalchemy.sql.sqltypes``, ``sqlalchemy.sql.schema`` and ``sqlalchemy.sql.ddl``, the last of which was moved from ``sqlalchemy.engine``. ``sqlalchemy.sql.expression`` is also a namespace now which pulls implementations mostly from ``sqlalchemy.sql.elements``, ``sqlalchemy.sql.selectable``, and ``sqlalchemy.sql.dml``. Most of the "factory" functions used to create SQL expression objects have been moved to classmethods or constructors, which are exposed in ``sqlalchemy.sql.expression`` using a programmatic system. Care has been taken such that all the original import namespaces remain intact and there should be no impact on any existing applications. The rationale here was to break out these very large modules into smaller ones, provide more manageable lists of function names, to greatly reduce "import cycles" and clarify the up-front importing of names, and to remove the need for redundant functions and documentation throughout the expression package.
* - endless isinstance(x, str)s....Mike Bayer2013-04-281-2/+8
|
* - the raw 2to3 runMike Bayer2013-04-271-5/+5
| | | | - went through examples/ and cleaned out excess list() calls
* - Fixed bug in unit of work whereby a joined-inheritanceMike Bayer2013-04-011-5/+2
| | | | | | | | | | | subclass could insert the row for the "sub" table before the parent table, if the two tables had no ForeignKey constraints set up between them. Also in 0.7.11. [ticket:2689] - fix a glitch in the assertsql.CompiledSQL fixture regarding when a multiparam compiledSQL is used within an AllOf - add a new utility function randomize_unitofwork() which does the function of --reversetop
* - add a nose runner that erases out argv, otherwiseMike Bayer2013-03-251-1/+0
| | | | | you get "import test" as what it tries to run with setup.py test
* - add support for pulling in an external requirements fileMike Bayer2013-02-061-3/+16
| | | | - start filling in default versions of remaining requirements that are still only in test/
* Fixed table reflection for Oracle when accessing a synonym that refersMike Bayer2012-12-091-2/+8
| | | | | | | | | | to a DBLINK remote database; while the syntax has been present in the Oracle dialect for some time, up until now it has never been tested. The syntax has been tested against a sample database linking to itself, however there's still some uncertainty as to what should be used for the "owner" when querying the remote database for table information. Currently, the value of "username" from user_db_links is used to match the "owner". [ticket:2619]
* juts a 'expected 2 blank lines' pep8 passDiana Clarke2012-11-191-1/+16
|
* - support "fails_if" requirements as __requires__; so far this just skips, ↵Mike Bayer2012-11-121-1/+6
| | | | | | | | | | doesn't actually run the test - add requirements for date/datetime/time capabilities - remove test/sql/test_types->DateTest and create new tests in suite/test_types - move the StringTest with the "no length create" test to the suite, though this is a weird test
* - [feature] Various API tweaks to the "dialect"Mike Bayer2012-10-081-6/+16
| | | | | | | API to better support highly specialized systems such as the Akiban database, including more hooks to allow an execution context to access type processors.
* - add back __engine_options__Mike Bayer2012-10-041-7/+20
| | | | | - break test_insert tests into explicitly get_lastrowid() vs. implicit_returning tests, fix up requirements to split them out
* - connect immediately on _create_testing_engine to initialize dialect ↵Mike Bayer2012-10-041-0/+1
| | | | capabilities
View Lorry Controller Status