I\'m trying out mock/responsibility driven d开发者_开发技巧esign. I seem to have problems to avoid returning mocks from mocks in the case of objects that need a service to retrieve other objects.
This is probably crazy. I want to take the idea of Dependency Injection to extremes. I have isolated all System.IO-related behavior into a single class so that I can mock that class in my other class
Our team is willing to unit-test a new code written under a running project extending an existing huge Oracle system.
In VisualStudio2010 Ultimate RC I cannot figure out how to suppress {\"CollectionAssert.AreEqual failed. (Element at index 0 do not match.)\"}
I\'m just getting started with TDD and am curious as to what approaches others take to run开发者_如何学C their tests. For reference, I am using the google testing framework, but I believe the question
I am writing some unit tests and I\'m getting an exception thrown from my real code when trying to do the following:
I\'m curious what a reasonable / typical value is for the ratio of test code to production code when people are doing TDD.Looking at one component, I have 530 lines of test code for 130 lines of produ
I know I 开发者_如何学Gowouldn\'t need this with Typemock, however, with something like MoQ , I need to use the adapter pattern to enable the creation of mocks via interfaces for code I don\'t control
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references,or expertise, but this question will likely solicit debate, a
I participate in a TDD Coding Dojo, where we try to practice pure TDD on simple problems. It occured to me however that the code which emerges from the unit tests isn\'t the most efficient.Now this is
加载中,请稍侯......