Jump to revision: | |
---|---|
Author: | pje |
Date: | Fri Nov 14 22:54:16 2003 UTC (20 years, 4 months ago) |
Log Message:
Added 'peak.util.mockdb', a "mock object" implementation of a DBAPI 2.0 driver module. 'mockdb' connections can be told to 'expect()' queries and 'provide()' data to their callers, and will raise AssertionErrors when they are used in a way that doesn't conform to your supplied expectations. This is intended to be used for unit testing components that depend on a database connection: you can verify that they send the right SQL, and you can provide them with dummy data to use. There is also a 'mockdb:' URL and peak.storage driver, so you can easily use a mock DB connection in place of a real one within a PEAK application, for testing purposes. Note, however, that 'peak.util.mockdb' is a DBAPI 2.0 driver in itself, and thus can also be used to test DBAPI usage outside of PEAK.
Changed paths:
Path | Action | Text Changes | Prop Changes | Diff to Previous |
---|---|---|---|---|
PEAK/CHANGES.txt | modified | X | (diff to previous) | |
PEAK/src/peak/peak.ini | modified | X | (diff to previous) | |
PEAK/src/peak/storage/SQL.py | modified | X | (diff to previous) | |
PEAK/src/peak/util/mockdb.py | added | X | X | |
PEAK/src/peak/util/tests/__init__.py | modified | X | (diff to previous) | |
PEAK/src/peak/util/tests/test_mockdb.py | added | X | X |
cvs-admin@eby-sarna.com Powered by ViewCVS 1.0-dev |
ViewCVS and CVS Help |