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
An alternative to ArgumentMatcher is ArgumentCaptor. Official example: ArgumentCaptor<Person> argument = ArgumentCaptor.forClass(Person.class); verify(mock).doSomething(argument.capture()); assertEquals(“John”, argument.getValue().getName()); A captor can also be defined using the @Captor annotation: @Captor ArgumentCaptor<Person> captor; //… MockitoAnnotations.initMocks(this); @Test public void test() { //… verify(mock).doSomething(captor.capture()); assertEquals(“John”, captor.getValue().getName()); }
when( fooDao.getBar( any(Bazoo.class) ) ).thenReturn(myFoo); or (to avoid nulls): when( fooDao.getBar( (Bazoo)notNull() ) ).thenReturn(myFoo); Don’t forget to import matchers (many others are available): For Mockito 2.1.0 and newer: import static org.mockito.ArgumentMatchers.*; For older versions: import static org.mockito.Matchers.*;
I’m not sure why py.test does not add the current directory in the PYTHONPATH itself, but here’s a workaround (to be executed from the root of your repository): python -m pytest tests/ It works because Python adds the current directory in the PYTHONPATH for you.
I’ve had good success using Mockito. When I tried learning about JMock and EasyMock, I found the learning curve to be a bit steep (though maybe that’s just me). I like Mockito because of its simple and clean syntax that I was able to grasp pretty quickly. The minimal syntax is designed to support the … Read more
The nested generics-problem can be avoided with the @Captor annotation: public class Test{ @Mock private Service service; @Captor private ArgumentCaptor<ArrayList<SomeType>> captor; @Before public void init(){ MockitoAnnotations.initMocks(this); } @Test public void shouldDoStuffWithListValues() { //… verify(service).doStuff(captor.capture())); } }
This works as you suggest – you just have to specify the class name as well: python testMyCase.py MyCase.testItIsHot
You need an additional library for code coverage, and you are going to be blown away by how powerful and easy istanbul is. Try the following, after you get your mocha tests to pass: npm install nyc Now, simply place the command nyc in front of your existing test command, for example: { “scripts”: { … Read more
With the latest version of Moq(4.2.1312.1622), you can setup a sequence of events using SetupSequence. Here’s an example: _mockClient.SetupSequence(m => m.Connect(It.IsAny<String>(), It.IsAny<int>(), It.IsAny<int>())) .Throws(new SocketException()) .Throws(new SocketException()) .Returns(true) .Throws(new SocketException()) .Returns(true); Calling connect will only be successful on the third and fifth attempt otherwise an exception will be thrown. So for your example it would … Read more
You’re approaching this the wrong way. Just test your functionality: if an exception is thrown the test will automatically fail. If no exception is thrown, your tests will all turn up green. I have noticed this question garners interest from time to time so I’ll expand a little. Background to unit testing When you’re unit … Read more