I do make unit testing by hitting the database. All of my om tests inherit from a specific TestOM class which records all test database records and delete them in the teardown function. Of course, these unit tests are executed in the development database and not in the deployment database.
Frederic Rex Madden wrote: >Hi, > >I've been using Turbine without a database for a little while and just >started to take a look at torque for my persistence layer. I do a lot >of automated unit testing in my apps and was wondering how people >approached testing on top of the peer objects. Usually, I try to write >the bulk of my tests to not actually hit the database, since opening a >connection to the db slows things down. More often than not, this is >done with Mock Objects. However, looking at Torque, it seems that there >aren't many interfaces to mock up. In addition, the generated peer >classes all deal with the Torque singleton, which also poses some >problems. > >So my questions: > >Is anyone doing XP type testing out there with Torque WITHOUT hitting >the database? >If not, what kind of approaches have people been using for db testing? > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
