Unit testing of DAO -

it first time make unit testing i'm trying find references how make unit testing of dao. can guys make simple example of setupbeforeclass, setup , how test method inserting new data in database using model this. simple example using easy mock. thank consideration

the idea of using mock objects perform unit testing strikes me peculiar doing testing mock objects instead of real ones. if think need use mock objects emulate database access entire architecture wrong. build software using 3-tier architecture can have many objects in business layer, 1 object in data access layer. if wanted exchange real database access dummy database access make change? 200+ objects in business layer, or 1 object in data access layer? why should implement mechanism change every object within application when need change one?

controllers meant integration tested, not unit tested. testing pyramid prescribes unit level focus should be, people sucked default.

assertions should never fail under circumstance. if fail in tests, indicates logical error. basically, if function doing "assert( 0 )" instead of returning error code, function should re-written.

can make massive changes class definition — throw out whole thing , replace different implementation — without impacting of code uses class's objects?

as has unfortunately happened variety of patterns originate rigid languages java, dependency injection has spread , been advocated cross-language best practice on trumped benefits of flexibility , malleability.

references

• dependency injection evil - tony marston

• test induced design damage - david heinemeier hansson

• tdding getters , setters considered harmful

• why getter , setter methods evil

• dependency injection not virtue in ruby (dhh)

• tdd rite way – javascript scene – medium

• 5 common misconceptions tdd & unit tests – javascript scene – medium

• ned batchelder: tl;dw: stop mocking, start testing

• accu :: mocks bad, layers bad

• google testing blog: testing on toilet: don’t overuse mocks