What Ruby on Rails TDD 101 article should I read? I will start with a guide to testing rails applications. Also Railscast has some excellent screencasts about how to use different testing tools. What do I need to test? I will start with models, since they are easy to test. The simple rule is that … Read more
Mock object replace mocked class entirely, returning recorded or default values. You can create mock out of “thin air”. This is what is mostly used during unit testing. When spying, you take an existing object and “replace” only some methods. This is useful when you have a huge class and only want to mock certain … Read more
There’s a compromise. Your coworker is actually onto something, but I think he’s doing it wrong. I’m not sure that totally random testing is very useful, but it’s certainly not invalid. A program (or unit) specification is a hypothesis that there exists some program that meets it. The program itself is then evidence of that … Read more
If you want to do “real” TDD (read: test first with the red, green, refactor steps) then you also have to start using mocks/stubs, when you want to test integration points. When you start using mocks, after a while, you will want to start using Dependency Injection (DI) and a Inversion of Control (IoC) container. … Read more
Second Class Citizens – test code isn’t as well refactored as production code, containing a lot of duplicated code, making it hard to maintain tests.
If you want to unit test a private method, something may be wrong. Unit tests are (generally speaking) meant to test the interface of a class, meaning its public (and protected) methods. You can of course “hack” a solution to this (even if just by making the methods public), but you may also want to … Read more
Internal classes need to be tested and there is an assembly attribute: using System.Runtime.CompilerServices; [assembly:InternalsVisibleTo(“MyTests”)] Add this to the project info file, e.g. Properties\AssemblyInfo.cs, for the project under test. In this case “MyTests” is the test project.
Karma or Protractor Karma is a JavaScript test-runner built with Node.js and meant for unit testing. The Protractor is for end-to-end testing and uses Selenium Web Driver to drive tests. Both have been made by the Angular team. You can use any assertion-library you want with either. Screencast: Karma Getting started related: Should I be … Read more
Even more meaningful : import static org.mockito.Mockito.never; import static org.mockito.Mockito.verify; // … verify(dependency, never()).someMethod(); The documentation of this feature is there ยง4 “Verifying exact number of invocations / at least x / never”, and the never javadoc is here.
If you have somewhat of a legacy Java application, and you’re not allowed to change the visibility of your methods, the best way to test private methods is to use reflection. Internally we’re using helpers to get/set private and private static variables as well as invoke private and private static methods. The following patterns will … Read more