You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now tests usually instantiate a Postgres or a SQLite interface, it would be cool if a test runner could be added that will set the environment variable to Postgres, then run all the tests and then set, the environment variable to SQLite and run all the tests, this way you would just have to modify one thing (like adding a MySQL dsn) and it would automatically run all the tests against the new environment variable.
Something like this should allow us to consolidate the Postgres gevent tests because they could be simplified to just another dsn.
For an example of a bad test that instantiates each is config_test.ObjectFieldTest
The text was updated successfully, but these errors were encountered:
…adds a test for issue #47 but I was only able to make the test fail one time while running the full suite, but never while running just the new test. Adds suport for non integer primary keys (maybe I should've lead with this)
Right now tests usually instantiate a Postgres or a SQLite interface, it would be cool if a test runner could be added that will set the environment variable to Postgres, then run all the tests and then set, the environment variable to SQLite and run all the tests, this way you would just have to modify one thing (like adding a MySQL dsn) and it would automatically run all the tests against the new environment variable.
Something like this should allow us to consolidate the Postgres gevent tests because they could be simplified to just another dsn.
For an example of a bad test that instantiates each is
config_test.ObjectFieldTest
The text was updated successfully, but these errors were encountered: