ansaurus

Question

Unit testing ModalWindow's content refresh fails while the actual functionality works as expected - what am I doing wrong?

Answer 1

+2 A:

I'm gonna go out on a limb here and say: Add your Panel component to a Page for testing..

AFAIK you can't test individual components, but should set up a test by getting a page and doing asserts on that..

This is what I use for testing:

public class TestHomePage {
    private static WicketTester tester;

    @BeforeClass
    public static void setUp() {
     tester = new WicketTester(new WicketApplication() {
      @Override
      protected void init() {
       //Override init to use SpringUtil's SpringContext due to missing WebApplicationContext
       addComponentInstantiationListener(new SpringComponentInjector(this, SpringUtil.getContext()));
      }
     });
    }

    @Test
    public void testRenderMyPage() {
     //start and render the test page
     tester.startPage(HomePage.class);

     //assert rendered page class
     tester.assertRenderedPage(HomePage.class);

     //assert page contents
     tester.assertContains("Welcome to my webpage");
    }
}

Please do correct me if I'm wrong!

Tim 2009-11-27 23:38:51

`WicketTester#startPanel()` actually adds the given panel to `DummyPanelPage` with the id `panel` to enable testing it as the single component on the page. I did however try using `Page` as `ModalWindow`'s content but that didn't work either.

Esko 2009-11-28 09:15:22

Ah ok, sorry I missed that.. Have you tried going around the test setup by keeping your modalwindowpanel as it is, and adding it to a `MyTestPage extends WebPage`? The WicketTester().startPanel does not seem to work from what you're telling me/us..

Tim 2009-11-28 11:19:31

Time flies, sorry :) Yes, I tried that too and got even more obscure errors.

Esko 2009-12-04 07:17:36

Hmm, just to eliminate any variables, have you tried UnitTesting the unaltered ModalWindow?

Tim 2009-12-04 08:21:41

I finally decided to accept this as answer even though the problem still persists; I'm assuming the issue here is actually a defect in the component itself and after I had extensively tested this I noticed that Wicket doesn't actually replace the component's contents but instead creates a new modal component on top of the existing one without closing the old cleanly. Oh well.

Esko 2010-06-25 13:37:12

Answer 2

+1 A:

The "production" code shown that ostensibly works is inconsistent. I suspect the variable campaignForm is supposed to be the field form.

But I think the root problem is that the modal window itself is nowhere actually attached to a component, and thus cannot be rendered.

If in the real code, it's attached somewhere outside your MyModalWindowPanel component, you'll definitely need to attach it somewhere in the test as well, likely by making your test build either a test page or a test panel that contains both the modal window and the component under test.

Don Roby 2009-11-29 13:45:34

Answer 3

+1 A:

The only time I've gotten that "No Page Found" exception was when trying to call getPage() in a panel constructor. The constructor is executed before the panel gets added to a page, so nothing is found... Are you perhaps doing something like that? Perhaps this code works in production, but is still throwing that error behind the scenes?

I know it's not what you are looking for, but I've found Selenium to be a great tool for testing web UI's. JUnit is awesome for testing logic, but Selenium is better suited for making sure the right thing displays in your UI. It looks hinky with it's gui interface and such, but it works great, and if you dig a bit the scripting api is easily accessible.

perilandmishap 2009-12-03 23:19:52

That was my initial reaction too and I made sure that's not the problem here. I don't know if `ModalWindow` internals do that though, I think I'll have to check that next.

Esko 2009-12-04 07:17:06

ansaurus

tags:

views:

answers:

Unit testing ModalWindow's content refresh fails while the actual functionality works as expected - what am I doing wrong?

related questions