[jira] [Commented] (WICKET-6856) WicketTester fails do startComponentInPage() after session invalidation

["Ilia Naryzhny (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/WICKET-6856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17239873#comment-17239873 ] 

Ilia Naryzhny commented on WICKET-6856:
---------------------------------------

Please find demo of test-cases which are failing in the following demo project: https://github.com/PhantomYdn/wicket-bugs/blob/master/pageexpired/src/test/java/org/orienteer/TestHomePage.java

Apparently, it's not so easy... Sometimes startPage also fails. Still trying to figure out actual root-cause... 

> WicketTester fails do startComponentInPage() after session invalidation
> -----------------------------------------------------------------------
>
>                 Key: WICKET-6856
>                 URL: https://issues.apache.org/jira/browse/WICKET-6856
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket-core
>    Affects Versions: 8.11.0
>            Reporter: Ilia Naryzhny
>            Priority: Major
>
> Probably issue WICKET-6848 introduced the following issue. If there is a code which does session invalidation first and then starts testing of a component: the last one will fail.
> Simple example:
> {code:java}
> tester.getSession().invalidate();
> tester.startComponentInPage(new AnyPanel("panel"));
> {code}
> But, at the same time starting pages (by class or instance) do not have this negative side effect.
> P.S. Doing `invalidateNow()` will help to solve this particular case, but in our case exactly invalidate() invoked as part of signout - so not a part of actual test case code.
> P.P.S Wicket 8.10.0 didn't have this problem,



--
This message was sent by Atlassian Jira
(v8.3.4#803005)