How to unit test a class which is just an adapter that logs input and output to a third-party library?
I have the following (in C#, but the question could also apply to Java):
Interfaces, Adapters, exposing business objects via WCF design
I know there have been countless discussions about this but I think this question is slightly different and may perhaps prompt a heated discussion (lets keep it friendly).
What is the point behind building an abstraction layer PDO Adapter class instead of using native PDO?
I have built a PDO adapter class because I thought, at the time anyway, it would be a good idea. After fighting with it, it makes no sense to me. Isn’t the design of PDO the way it is to keep you from having to create special adapters for a given database?
What is the point behind building an abstraction layer PDO Adapter class instead of using native PDO?
I have built a PDO adapter class because I thought, at the time anyway, it would be a good idea. After fighting with it, it makes no sense to me. Isn’t the design of PDO the way it is to keep you from having to create special adapters for a given database?
What pattern do I use and how do I implement it for one method that will be handled multiple ways
My scenario: I am creating an application that will allow me to create a mapping of redirect url’s that will point from the request url (the url in the old ecommerce solution) to the target url. There will be multiple implementations as we have multiple ecommerce solutions that were moving to our new one.
What pattern do I use and how do I implement it for one method that will be handled multiple ways
My scenario: I am creating an application that will allow me to create a mapping of redirect url’s that will point from the request url (the url in the old ecommerce solution) to the target url. There will be multiple implementations as we have multiple ecommerce solutions that were moving to our new one.