Unit tests tell a developer that the code is doing things right; functional tests tell a developer that the code is doing the right things. You can read more at Unit Testing versus Functional Testing A well explained real-life analogy of unit testing and functional testing can be described as follows, Many times the development … Read more
This prose by Alberto Savoia answers precisely that question (in a nicely entertaining manner at that!): http://www.artima.com/forums/flat.jsp?forum=106&thread=204677 Testivus On Test Coverage Early one morning, a programmer asked the great master: “I am ready to write some unit tests. What code coverage should I aim for?” The great master replied: “Don’t worry about coverage, just write … Read more
Mock objects are useful when you want to test interactions between a class under test and a particular interface. For example, we want to test that method sendInvitations(MailServer mailServer) calls MailServer.createMessage() exactly once, and also calls MailServer.sendMessage(m) exactly once, and no other methods are called on the MailServer interface. This is when we can use … Read more
A unit test is a test written by the programmer to verify that a relatively small piece of code is doing what it is intended to do. They are narrow in scope, they should be easy to write and execute, and their effectiveness depends on what the programmer considers to be useful. The tests are … Read more
Ask yourself a single question: What are you going to test? You mentioned FakeContext and Mocking the context – why to use both? Those are just different ways to do the same – provide test only implementation of the context. There is one more bigger problem – faking or mocking context or set has only … Read more
Let me begin by plugging sources – Pragmatic Unit Testing in Java with JUnit (There’s a version with C#-Nunit too.. but I have this one.. its agnostic for the most part. Recommended.) Good Tests should be A TRIP (The acronymn isn’t sticky enough – I have a printout of the cheatsheet in the book that … Read more
I get paid for code that works, not for tests, so my philosophy is to test as little as possible to reach a given level of confidence (I suspect this level of confidence is high compared to industry standards, but that could just be hubris). If I don’t typically make a kind of mistake (like … Read more
The key difference, to me, is that integration tests reveal if a feature is working or is broken, since they stress the code in a scenario close to reality. They invoke one or more software methods or features and test if they act as expected. On the opposite, a Unit test testing a single method … Read more
You can get some information : From Martin Fowler about Mock and Stub Fake objects actually have working implementations, but usually take some shortcut which makes them not suitable for production Stubs provide canned answers to calls made during the test, usually not responding at all to anything outside what’s programmed in for the test. … Read more
Every day in our office there is an exchange which goes something like this: “Man, I just love unit tests, I’ve just been able to make a bunch of changes to the way something works, and then was able to confirm I hadn’t broken anything by running the test over it again…” The details change … Read more