Data Layer Testing: Test Inheritance Patterns

re: Data Layer Testing: Test Inheritance Patterns

RoyOsherove — Thu, 20 Dec 2007 15:25:40 GMT

Jason:

either you derive and implement the abstract method with nothing in the body, or create a separate utility class for your scenarios..

re: Data Layer Testing: Test Inheritance Patterns

Jason — Thu, 20 Dec 2007 14:37:29 GMT

Yes, I am rolling everything back using what you call an "Abstract Utility Class". Our data layer uses the common approach of passing a generic type to provide CRUD functionality "for free" for a given entity. My question is really about YAGNI - should I write a test for functionality that I don't currently need?

Elegant Code » But the tests passed on my machine…

Elegant Code » But the tests passed on my machine… — Thu, 20 Dec 2007 02:05:10 GMT

Pingback from Elegant Code » But the tests passed on my machine…

re: Data Layer Testing: Test Inheritance Patterns

Jason — Wed, 19 Dec 2007 16:32:13 GMT

I have a question about the second and third patterns. Should I test delete for example if currently my application doesn't need to delete the entity?

The Daily Find #7 - TechToolBlog

The Daily Find #7 - TechToolBlog — Thu, 29 Nov 2007 14:10:02 GMT

Pingback from The Daily Find #7 - TechToolBlog