From: Abel Hunt "pndop@reset.com.pt"
Date: Oct 23, 2006 7:04 AM
Subject: flank
The trick to make it work is, again,. Second, there are too many bright people in the US writing on these things in the US, and I thought it would be easier to find my place in the French ecosystem. This community is to be used as a sounding board for every new initiative in the company regarding social collaboration tools. The derived "mock" implementation within the test may not be overriding anything in the superclass anymore, and the test may fail to execute the methods originally intended. Then what's more natural than moving the blog too? Get your brushes and submit your art!
Each time I stumble into something interesting on the Internet which I cannot process immediately, I bookmark it and tag it using my own keywords of the moment. Yes, the French do have this historical tendency to rebel against authority and at the same time to favor highly centralized forms of government. This is because you can't know whether your refactorings will break something without tests. While this is a noble goal, it is not the only good reason to use mocks. If your tests are simple, so will your code will be. I just wanted to argue that TDD does not slow you down. -Like always doing the simplest thing and continuosly refactor the code. Calling the CheeseDao. While this is a noble goal, it is not the only good reason to use mocks. Specifically, if the superclass is refactored, there is no guarantee that the test is still valid. He as many others seem to have misunderstood what it's all about. Gavin and Hibernate rock. If your tests are simple, so will your code will be. -A fairly common combination of technologies and patterns. NET and a Ruby port, and more in the pipe. The package scope is even com.
Check out QDox Attributes! -And hopefully encourage the development team to do something about it before it becomes too big a hassle. This can incur some percieved overhead in the codebase, as the developer will now have to maintain both a CheeseDao and a HibernateCheeseDao. It's called "Le prix de la confiance", which can be translated either by "The Price Of Trust" or "The Prize Of Trust". This will in the long run lead to SHORTER development time. Third, I love my country in spite of its errands, and I really would like France to embrace the knowledge economy a little more faster than it does today. After all, the overridden saveCheese method in the "mock" calls the superclass' method, right?
From: Abel Hunt "pndop@reset.com.pt"
Date: Oct 23, 2006 7:04 AM
Subject: flank
The trick to make it work is, again,. Second, there are too many bright people in the US writing on these things in the US, and I thought it would be easier to find my place in the French ecosystem. This community is to be used as a sounding board for every new initiative in the company regarding social collaboration tools. The derived "mock" implementation within the test may not be overriding anything in the superclass anymore, and the test may fail to execute the methods originally intended. Then what's more natural than moving the blog too? Get your brushes and submit your art!
Each time I stumble into something interesting on the Internet which I cannot process immediately, I bookmark it and tag it using my own keywords of the moment. Yes, the French do have this historical tendency to rebel against authority and at the same time to favor highly centralized forms of government. This is because you can't know whether your refactorings will break something without tests. While this is a noble goal, it is not the only good reason to use mocks. If your tests are simple, so will your code will be. I just wanted to argue that TDD does not slow you down. -Like always doing the simplest thing and continuosly refactor the code. Calling the CheeseDao. While this is a noble goal, it is not the only good reason to use mocks. Specifically, if the superclass is refactored, there is no guarantee that the test is still valid. He as many others seem to have misunderstood what it's all about. Gavin and Hibernate rock. If your tests are simple, so will your code will be. -A fairly common combination of technologies and patterns. NET and a Ruby port, and more in the pipe. The package scope is even com.
Check out QDox Attributes! -And hopefully encourage the development team to do something about it before it becomes too big a hassle. This can incur some percieved overhead in the codebase, as the developer will now have to maintain both a CheeseDao and a HibernateCheeseDao. It's called "Le prix de la confiance", which can be translated either by "The Price Of Trust" or "The Prize Of Trust". This will in the long run lead to SHORTER development time. Third, I love my country in spite of its errands, and I really would like France to embrace the knowledge economy a little more faster than it does today. After all, the overridden saveCheese method in the "mock" calls the superclass' method, right?