[
https://issues.apache.org/jira/browse/WICKET-5147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13640248#comment-13640248
]
Rob Audenaerde commented on WICKET-5147:
----------------------------------------
I do not destroy the WicketTester. But I also do not reuse the WicketTester
between tests. My UI tests use this piece of code:
@BeforeMethod
public final void setupTest() throws Exception
{
LOG.info( "Running test in class:" + this.getClass() );
this.wicketTester = new WicketTester( this.wicketApplication );
this.login();
}
Besides that, I see the number of cookies increase expontentially in my
testcase in the attached zip.
> WicketTester MockHttpRequest.getCookies very slow / OutOfMemory
> ---------------------------------------------------------------
>
> Key: WICKET-5147
> URL: https://issues.apache.org/jira/browse/WICKET-5147
> Project: Wicket
> Issue Type: Bug
> Affects Versions: 6.7.0
> Reporter: Rob Audenaerde
> Attachments: testcookies.zip
>
>
> We have an extensive set of WicketTester tests. Recently, the wicket RELEASE
> in the maven repository changed to 6.7.0. After the new version, our tests
> got very slow.
> When profiling, I discovered that the MockHttpRequest.getCookies() was taking
> up a lot of time. Also, tests failed because of OutOfMemory exceptions. My
> guess is that somehow a lot of objects are created at such speeds that the GC
> cannot clean them
> I will investigate further, but switching back to 6.6.0 solved the issue.
> [Edit]
> The tests are run with TestNG and using 'mvn test'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
