Am 05.01.2013 16:58, schrieb D'Arcy J.M. Cain:
According to ticket #9 we want to clean up test_pg.py and merge it with TEST_PyGreSQL_classic.py. Given that, shouldn't we start putting new tests into TEST_PyGreSQL_classic.py at least? In fact, if we modify a test in test_pg.py we should probably migrate it then.
I'd rather avoid to do that and merge them later in one go instead of maintaining two partially overlapping test suites trying to keep them in sync. That's unnecessary work and we will need to fully merge them later anyway, and that will only become more difficult.
The two test suites also use database schemes and fixtures which are different and both do not look optimal to me and should be reconsidered upfront (particularly in terms of performance, you don't want to recreate databases, schemas and tests newly for hundreds of tests).
-- Chris _______________________________________________ PyGreSQL mailing list [email protected] https://mail.vex.net/mailman/listinfo.cgi/pygresql
