[WICKET-3747] Namespace WicketTester methods to group them by functionality

• Type: Sub-task
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 1.5-RC4
• Component/s: wicket
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Martin Tzvetanov Grigorov
• Created: 27/May/11 07:05
• Updated: 03/Feb/12 10:21
• Resolved: 03/Feb/12 10:21

Description

Having 50+ public methods in WicketTester confuses the users. The IDE suggestion dropdown has many entries and it is hard to find what you need.
Introducing "namespace objects" like Application's I***Setting will improve this problem. Something like : tester.start().page(...), tester.start().componentInPage(...), tester.assert().isvisible(..), tester.assert().model(...), tester.execute().link(...), etc.
All of these "namespace methods" will do something like :
BaseWicketTester#assert()

{ return Assert(this)}

;
BaseWicketTester.Assert#isVisible

{tester.assertIsVisible(x)}

and BaseWicketTester#assertIsVisible will be made deprecated and either removed in later version or made private (hidden).

This way the IDE will suggest only #start(), #execute(), #assert(), etc. initially. Then when the user selects one of them the IDE will suggest only the methods related to this "namespace".