coverage is busted again, port the upcoming alembic approach over

Issue #3196 resolved
Michael Bayer
repo owner created an issue

at some point, when building the pytest suite the behavior that coverage started up before anything else went away. It seems that conftest importing sqlalchemy/testing is all that needs to happen to ruin it as apparently conftest is pulled in before coverage starts. I seriously thought I tested the crap out of this when i first did pytest but apparently I'm wrong.

upcoming in alembic is an old-is-new-again "bootstrap" solution, hacky like the old one but generalized a little more nicely to nose and pytest.

Comments (1)

  1. Michael Bayer reporter
    • remove some crufty old testing options
    • 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

    → <<cset d7498cf4adb8>>

  2. Log in to comment