use Perl

• Re: Browser based testing of your own code (Score:1)

  by daxim (8218) on 2009.11.16 7:33 (#71141) Homepage Journal

  i haven't seen a tool that automates konqueror, opera, explorer and mozilla.

  The heyday of Konqueror is over. Wouldn't you rather test with Webkit based browsers? http://seleniumhq.org/docs/01_introducing_selenium.html#supported-browsers [seleniumhq.org]

  X11::GUITest [...] provides the basics of being able to recognise a window and send keystrokes and mouse clicks to it, which should be enough.

  That's not enough at all. Dump of an Opera 10 application window that has loaded one document with a complex HTML form:

  > xwininfo -children
  
  xwininfo: Please select the window about which you
            would like information by clicking the
            mouse in that window.
  
  xwininfo: Window id: 0x4c0000c "test - Opera"
  
    Root window id: 0x82 (the root window) (has no name)
    Parent window id: 0x1e044da (has no name)
       8 children:
       0x4c00028 (has no name): ()  1672x27+0+0  +4+52
       0x4c00031 (has no name): ()  1x1+-1+-1  +3+51
       0x4c00030 (has no name): ()  862x961+0+28  +4+80
       0x4c00012 (has no name): ()  100x11+0+0  +4+52
       0x4c00011 (has no name): ()  1x961+862+28  +866+80
       0x4c00010 (has no name): ()  1x961+0+28  +4+80
       0x4c0000f (has no name): ()  862x1+0+989  +4+1041
       0x4c0000e (has no name): ()  862x1+0+27  +4+79

  Now guess which is what.

  the automation program must be able to recognise the correct page to the page to send input to, by clicking the mouse or tabbing.

  This is where each new browser needs to provide some initialisation data.

  Yes, but not in the complicated prone-to-fail way you think. Applications shall provide accessibility hooks. http://ldtp.freedesktop.org/ [freedesktop.org] http://en.wikipedia.org/wiki/Microsoft_Active_Accessibility [wikipedia.org] http://www.apple.com/accessibility/macosx/ [apple.com]

  Drivers such as accessibility aides or in our case testing frameworks then can interpret and manipulate any application elements (widgets, stuff on canvases or rendered areas) directly.

  i have a fair chance of being able to implement a pretty interesting version of the WWW::Mechanize

  Already done. Save yourself the trouble of re-inventing. http://google.com/search?q=mozrepl [google.com] http://search.cpan.org/dist/WWW-Mechanize-FireFox [cpan.org]

  Reply to This

  • Re: (Score:1)

    by daxim (8218)

    > xwininfo -children

    I made a mistake there, should have been -tree instead of -children. The argument still stands – the descendant windows have neither type nor name.