delta/python-packages/sqlalchemy.git/test/bootstrap/noseplugin.py, branch pr_github_285

trying different approaches to test layout. in this one, the testing modules

2012-09-27T06:37:33+00:00

become an externally usable package but still remains within the main sqlalchemy parent package.
in this system, we use kind of an ugly hack to get the noseplugin imported outside of the
"sqlalchemy" package, while still making it available within sqlalchemy for usage by
third party libraries.

- profile file is configurable

2012-09-26T23:15:09+00:00

- further reorganization of test suite:

2012-09-26T21:21:21+00:00

  - bootstrap and lib move to all absolute imports
  - testing.py is no longer internally referenced.
  - requirements move to be a pluggable class which can
    be overridden.
  - cleanup

in the interests of third party testing, test/lib and test/bootstrap
may move to be an independent package.

- fixes for mxODBC, some pyodbc

2012-09-02T19:14:09+00:00

- enhancements to test suite including ability to set up a testing engine
for a whole test class, fixes to how noseplugin sets up/tears
down per-class context

OK! let's turn this around completely. Forget making a single count across

2012-08-11T19:51:08+00:00

all platforms.  let's instead store callcounts for *all* observed platforms in a datafile.
Will try to get enough platforms in the file for jenkins to have meaningful results.
for platforms not in the file, it's just skiptest.

-whitespace bonanza, contd

2012-07-28T21:05:50+00:00

remove the "produce test" approach from the polymorphic_rel tests,

2012-02-28T21:13:26+00:00

break out fixtures into a separate module which will be
used by some future test suites as well

- rework the test suite to make use of SkipTest for tests skipped, unsupported, etc.

2012-01-22T18:19:22+00:00

so that we can get an accurate picture what's really running/not, what's installed on jenkins, etc.
Tested in cpython 2.7 so far, we'll see what jenkins says about other platforms

- given that Oracle's issue is not just open connections, but closed ones too, go really

2011-05-10T00:40:33+00:00

heavy handed and start marking tests as "requires.ad_hoc_engines", add a flag --low-connections
that will switch the engine reaper mechanism to use as *few* distinct engines and connections
as possible, many engine tests that really need their own engines are just skipped.

- hardcore force every connection into a strong-referenced set, rollback on every test, close on every context.

2011-04-26T01:50:26+00:00

this uses pool events but bypasses the pool's fairy/record/dispose services.   pypy still seems to expose
some holes in that at least as far as what some (or maybe just one, cant find it yet) of the tests does.
haven't tested this too deeply, just on sqlite + postgres, cypthon 2.7 + pypy.   will see what the buildbot
says