Unit Test for readonly database -
we writing application accessing database of erp-solution. of course not allowed write database (database = readonly).
this leads conflict when writing tests our daos access/read database.
what best practices generate testdata?
any suggestions appriciate, in advance tobi
update: maybe important, don't map properties of tables in erp's database because won't need them. of not mapped columns not null.
use non production database. if possible use in-memory database, use db unit create schema , standing data , let instance tear down when test pack complete.
Comments
Post a Comment