java - Mockito InvocationImpl retained across TestSuite tests -


i have junit test suite ~800 tests. of these wired spring , large number use mockito mock/spy behavior. started running out of memory errors. while analyzing hprof dump noticed > 30% of heap consumed mockito invocationimpls retained between tests.

is there way clear these after test class completes? not want use mockito.reset( mock ) mocks initialization varies each test. if not, appears need split tests accommodate leak.

from this link appears mockito team recognizes these retained trade-off of verification after execution approach. i'm wondering if has found means clear these large number of unit tests can strung in suite.

i found partial work around. in case vast majority of invocationimpl instances being created during single test case used spy() create real partial mock 1 method overridden. using mockito 1.10.19, switched partial mock construction spy() mock( <class>, withsettings().spiedinstance( realinstance ).defaultanswer( calls_read_mathods ).stubonly() ).

while prevents use of verify() on mock, stubonly() keeps mock storing instances of invocationimpl each call made spy during test, , decreased heap use.

since mocks created springockito in spring context files, needed ugly rework of bean definition match mock() call, follows. allows spy used in spring-wired domain classes.

  <bean id="realinstance" class="<real instance class>" />   <bean id="instspysettings" class="org.mockito.mockito" factory-method="withsettings" />   <bean id="instspypartialmock" factory-bean="instspysettings" factory-method="spiedinstance">     <constructor-arg>       <ref local="realinstance" />     </constructor-arg>   </bean>   <bean id="instspydefaultanswers" factory-bean="instspypartialmock" factory-method="defaultanswer">     <constructor-arg><util:constant static-field="org.mockito.mockito.calls_real_methods"/></constructor-arg>   </bean>   <bean id="instspystubonly" factory-bean="instspydefaultanswers" factory-method="stubonly" />   <bean id="spyinstance" class="org.mockito.mockito" factory-method="mock">     <constructor-arg value="<real instance class>" />     <constructor-arg>       <ref local="instspystubonly" />     </constructor-arg>   </bean>

Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more