Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make tests more flexible to multiple interfaces #39

Closed
Jaymon opened this issue Feb 14, 2017 · 1 comment
Closed

Make tests more flexible to multiple interfaces #39

Jaymon opened this issue Feb 14, 2017 · 1 comment

Comments

@Jaymon
Copy link
Owner

Jaymon commented Feb 14, 2017

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

Jaymon added a commit that referenced this issue Jul 8, 2017
…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)
@Jaymon
Copy link
Owner Author

Jaymon commented Mar 11, 2023

This has been mostly taken care of with EnvironTestCase that runs all the tests for each found PROM_TEST_DSN

@Jaymon Jaymon closed this as completed Mar 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant