[WICKET-5389] Allow continued processing with WicketTester after exception is thrown

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 6.11.0, 7.0.0-M1
• Fix Version/s: 7.0.0-M1
• Component/s: wicket
• Assignee: Sven Meier
• Reporter: Sven Meier
• Created: 17/Oct/13 11:49
• Updated: 05/Sep/18 07:04
• Resolved: 17/Oct/13 14:56

Description

When exposing an exception while processing, WicketTester is left in an inconsistent state. Since #setupNextRequestCycle() is not called, no additional processing is possible afterwards:

org.apache.wicket.WicketRuntimeException: No RequestCycle is currently set!

For tests expecting WicketTester#process() to fail, it would be nice to be able to continue processing with the same tester instance afterwards.

Issue Links

• is related to: WICKET-6053 Allow to reuse the same application instance in several tests