Tapestry 5
  1. Tapestry 5
  2. TAP5-161

Devise test stategy for DateField and other DHTML/JS intensive components

    Details

    • Type: Task Task
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 5.0.15
    • Fix Version/s: 5.3
    • Component/s: None
    • Labels:
      None

      Description

      The new DateField component is difficult to test inside Selenium because Selenium doesn't track what occurs after the user clicks the trigger button. Not sure how to make that work, it may require an upgrade to a newer version of selenium.

        Activity

        Show
        Howard M. Lewis Ship added a comment - http://agiletesting.blogspot.com/2006/03/ajax-testing-with-selenium-using_21.html
        Hide
        Howard M. Lewis Ship added a comment -

        I believe Seleniums' waitForCondition is used to handle this situation.

        Show
        Howard M. Lewis Ship added a comment - I believe Seleniums' waitForCondition is used to handle this situation.
        Show
        Howard M. Lewis Ship added a comment - Made some progress on this: http://tapestryjava.blogspot.com/2008/08/ajax-and-selenium-waitforcondition.html
        Hide
        Massimo Lusetti added a comment -

        DateField always cause issues

        Show
        Massimo Lusetti added a comment - DateField always cause issues
        Hide
        Robert Zeigler added a comment -

        Re-open to update fix status.

        Show
        Robert Zeigler added a comment - Re-open to update fix status.
        Hide
        Robert Zeigler added a comment -

        This has largely been resolved for real. When I fixed TAP5-1408 and TAP5-1409, I wrote a couple of fairly extensive tests for the component, including making sure that the proper date is selected in the popup, selecting a date in the popup puts the proper date in the text field, etc. Any further tests will need to be written on a case-by-case basis: as a bug crops up, we add a new test.

        Show
        Robert Zeigler added a comment - This has largely been resolved for real. When I fixed TAP5-1408 and TAP5-1409 , I wrote a couple of fairly extensive tests for the component, including making sure that the proper date is selected in the popup, selecting a date in the popup puts the proper date in the text field, etc. Any further tests will need to be written on a case-by-case basis: as a bug crops up, we add a new test.
        Hide
        Howard M. Lewis Ship added a comment -

        Great work!

        Show
        Howard M. Lewis Ship added a comment - Great work!

          People

          • Assignee:
            Robert Zeigler
            Reporter:
            Howard M. Lewis Ship
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development