Functional test warning when app uses SQLAlchemy and binds engine

[domenkozar]

Anonymous:

I'm getting the following warning:
SAWarning: At least one scoped session is already present.
configure() can not affect sessions that have already been created.

The Warning is raised when TestApp.post() or .get() is called
for the SECOND time in the life of entire test, but only once. The
warning is raised at the second of these two lines of code:

DBSession = scoped_session(sessionmaker(extension=ZopeTransactionExtension())) DBSession.configure(bind=engine)

This code is called ONCE per application startup (per default
Pyramid pyramid_routesalchemy template setup).

URL: https://bitbucket.org/ianb/webtest/issue/27/functional-test-warning-when-app-uses

[domenkozar]

This is something a user should handle, nothing in the scope of WebTest. Indeed, SQLAlchemy raises a warning when you try to configure an engine for the second time.

[fweep]

I'm having the same problem with my WebTest tests. Stumbled on this while Googling, and still haven't found a solution. If anyone stops by here and knows how to resolve this, please comment.

[domenkozar]

put a pdb when you assemble the session, run the tests and you'll see when it's called for the second time

[dobesv]

You can call DBSession.remove() prior to calling DBSession.configure() in your test set up code.

[crooksey]

@dobesv Thanks, that's awesome, anyone +1 to put this in the webtest docs?