[jira] [Resolved] (WICKET-3747) Namespace WicketTester methods to group them by functionality

["Martin Grigorov (Resolved) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-3747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Martin Grigorov resolved WICKET-3747.
-------------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 6.0.0)

No real need to make this change
                
> Namespace WicketTester methods to group them by functionality
> -------------------------------------------------------------
>
>                 Key: WICKET-3747
>                 URL: https://issues.apache.org/jira/browse/WICKET-3747
>             Project: Wicket
>          Issue Type: Sub-task
>          Components: wicket
>    Affects Versions: 1.5-RC4
>            Reporter: Martin Grigorov
>            Assignee: Martin Grigorov
>            Priority: Minor
>
> 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(x) {tester.assertIsVisible(x)} 
> and BaseWicketTester#assertIsVisible(x) 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". 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira