John Ralls <[email protected]> writes: > Yeah, don't. That is, don't actually talk to the real databases, just write > a trivial pretend database (they're often called mocks) with the same > function signatures and header names and so on so that you can build your > test program with it instead of with pgsql or mysql. (Trivial so that the > mock database doesn't need to be tested itself.) Ideally you should do the > same for sqlite.
I would only recommend this if you find that using (one of the) real DB backends (sqlite, and against a /dev/shm-based db in particular) for day-to-day testing is not fast enough. Maintaining an ad-hoc persistence backend is a huge PITA … in many systems, though, it's less of a PITA than a disruptively-long-running testsuite. -- ...jsled http://asynchronous.org/ - a=jsled; b=asynchronous.org; echo $...@${b}
pgp7uK1PrQoeg.pgp
Description: PGP signature
_______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
