-
```
The following code:
ArgumentCaptor capturedCount = new ArgumentCaptor();
verify(mock).someMethod(capturedCount.capture());
will throw an NPE on the verify line if someMethod() takes a pr…
-
```
I am sure there is a valid reason but I dont know it. In the java bean code
generation you use this to map primitives to integers:
map_primitive_wrapper ::= [
"int": "Integer",
"long": "…
-
```
The following code:
ArgumentCaptor capturedCount = new ArgumentCaptor();
verify(mock).someMethod(capturedCount.capture());
will throw an NPE on the verify line if someMethod() takes a pr…
-
```
Using Hamcrest with primitive types often requires auto boxing/unboxing to the
corresponding reference types. Hidden NullPointerExceptions are just one of
quite a few concerns regardings automat…
-
```
Say I have a
@Captor ArgumentCaptor fooCaptor;
I'd like to have it capture primitive double arguments, but the annotation
gives me an Object captor.
Unfortunately this also fails in a non-obviou…
-
```
Pattern: Method invokes inefficient Number constructor; use static valueOf
instead
id: DM_NUMBER_CTOR, type: Bx, category: PERFORMANCE
Using new Integer(int) is guaranteed to always result in a…
-
```
It would be useful to have the behaviour for computing hashcodes as recommended in Effective
Java Item 8 included as a library function. See
http://java.sun.com/developer/Books/effectivejava/C…
-
```
Say I have a
@Captor ArgumentCaptor fooCaptor;
I'd like to have it capture primitive double arguments, but the annotation
gives me an Object captor.
Unfortunately this also fails in a non-obviou…
-
```
Say I have a
@Captor ArgumentCaptor fooCaptor;
I'd like to have it capture primitive double arguments, but the annotation
gives me an Object captor.
Unfortunately this also fails in a non-obviou…
-
```
Say I have a
@Captor ArgumentCaptor fooCaptor;
I'd like to have it capture primitive double arguments, but the annotation
gives me an Object captor.
Unfortunately this also fails in a non-obviou…