In JUnit FAQ you can read that you shouldn\'t test methods that are too simple to break. While all examples seem logical (getters and setters, delegation etc.), I\'m not sure I am able to grasp the \"
I googled and read some good answers/posts on IOC a开发者_JS百科nd do understand the overall concept. I have an existing framework (not very well designed) and TDD is an after thought to write some NU
I am unit testing an ICustomerRepository interface used for retrieving objects of type Customer. As a unit test what value am I gaining by testing the ICustomerRepository in this manner?
I am attempting to test the Index action of a controller. The action uses AutoMapper to map a domain Customer object to a view model TestCustomerForm. While this works I am concerned about the best wa
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
My controllers are utilizing StructureMap开发者_运维知识库 and AutoMapper. Presently, there is nothing exceptional with my routes. For the basic CRUD controller actions what tests should I be writing
Consider this code: public void actionPerformed(ActionEvent e) { setEnabled(false); new SwingWorker<File, Void>() {
I am trying to use Rhino.Mocks to mock up a ControllerContext object to gain access to runtime objects like User, Request, Response, and Session in my controller unit tests. I\'ve written the below me
I\'m learning TDD, and I have a question about private / protected variables. My question is: If a function I want to test is operating on a private variable, how should I test it?
It seems exceptionally heavy handed but going by the rule anything publicly available should be tested should auto-implemented properties be tested?
加载中,请稍侯......