I still dont get it, maybe I miss something but I think that borders also have everything they need to render them selves. When you provide empty body to border it will render itself and you will be able to test it (the same way you test panel). I know that sometimes it will be nesessery to provide some expected body to border to test it(and then probably you are forced to write some panel/page) but there are cases when you could test it with some stub, static, hardcoded body. I know that now it is possible to test such borders so its not limitation of WicketTester but it would be conveniently if WicketTester could support testing borders with some predefined body easiler. Its not about limitation of WicketTester ,its about providing functionality to easier test such borders. What do you think about it ?
I know that it is possible to create a generic panel/page to test borders but it is also easy to create generic page to work with panels, but despite this WicketTester provides method to test panels but doesnt provide similar method to test borders(borders which you could test with some stub body). igor.vaynberg wrote: > > self contained in that the page and panel has everything they need to > render themselves. a border is meant to be embedded in a page or > panel, not work independently. anyways, its really easy to create a > generic panel to facilitate the testing of borders. > > -igor > > On Sun, Nov 2, 2008 at 2:57 AM, Daniel Lipski > <[EMAIL PROTECTED]> wrote: >> >> Sorry, but I dont get your point... >> What do you mean self contained (in terms of Wicket API) ? >> >> Im sure there is a lot of user created border components which contain a >> lot >> of surrounding markup and components and it is very desireble(at least >> for >> me :)) to be able to 'unit' test such components with Wicket tester, >> regardles (i.e with empty) to border body. >> Does method Im looking for was not provided because of technical problems >> ? >> If so what is the simplest way to test border components (surrounding >> markup >> and components) with i.e empty body ? >> >> Regards >> Daniel Lipski >> >> >> igor.vaynberg wrote: >>> >>> borders are not meant to be self-contained like panels. they are meant >>> to be used within something that contains markup, eg page or panel. >>> >>> -igor >>> >>> On Fri, Oct 31, 2008 at 8:14 AM, dlipski <[EMAIL PROTECTED]> >>> wrote: >>>> >>>> Hi >>>> >>>> Is it possible (if not why?) to test Border components in a way similar >>>> to >>>> testing Panels ? -WicketTester.startPanel(TestPanelSource) ? Its >>>> strange >>>> but I cant find corresponding method for Borders. >>>> >>>> Thanks in advance. >>>> >>>> Daniel Lipski >>>> -- >>>> View this message in context: >>>> http://www.nabble.com/testing-borders-with-WicketTester-tp20268028p20268028.html >>>> Sent from the Wicket - User mailing list archive at Nabble.com. >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>>> For additional commands, e-mail: [EMAIL PROTECTED] >>>> >>>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [EMAIL PROTECTED] >>> For additional commands, e-mail: [EMAIL PROTECTED] >>> >>> >>> >> >> -- >> View this message in context: >> http://www.nabble.com/testing-borders-with-WicketTester-tp20268028p20288374.html >> Sent from the Wicket - User mailing list archive at Nabble.com. >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/testing-borders-with-WicketTester-tp20268028p20298543.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
