[Windmill-dev] Testing an autocomplete widget

[Adam Christian]

I haven't tried anything yet, but for auto complete I think it would  
be useful to see the changes happening in the available options as you  
type. If not, that is easy to tailor.

On Dec 11, 2007, at 11:39 AM, Bobby Rullo wrote:

> Why the long wait? Have you tried just firing off the events rapid  
> fire in order?
>
> On Dec 11, 2007, at 11:34 AM, Adam Christian wrote:
>
>> Greetings,
>>
>> So at a first glance it looks like your JavaScript is being  
>> triggered by onkeypress, and since our type function simply sets  
>> the value via the DOM the onkeypress isn't being triggered.
>>
>> I am going to attempt writing an addition to our controller api  
>> that you can use instead of type, that will take a string and  
>> simulate pressing those keys with 1/3 second delays between to see  
>> if I can trigger your auto complete functionality.
>>
>> After that, selecting your target entry from the list should work  
>> out of the box as long as it is a standard HTML drop down, if not  
>> we can deal with that accordingly.
>>
>> I will send out another response once I get a chance to work on  
>> this hopefully this afternoon/evening.
>>
>> Thanks for checking out the project, and your patience.
>>
>> Adam Christian
>>
>> On Dec 11, 2007, at 11:08 AM, Robert Leftwich wrote:
>>
>>> I'm evaluating Windmill for testing a largish web app, but  
>>> unfortunately
>>> I'm failing at the first hurdle. We use autocomplete from the YUI
>>> library fairly extensively and I was wanting to test an instance  
>>> of it,
>>> but it seems that Windmill's 'type' method does not trigger the  
>>> widget.
>>> To simplify things I tried to test one of the examples on the YUI  
>>> site -
>>> http://developer.yahoo.com/yui/examples/autocomplete/ac_ysearch_json_clean.html
>>> - but the autocomplete list of possible search queries never  
>>> appears.
>>> Following is the simplest test I recorded:
>>>
>>> {"params": {"id": "ysearchinput"}, "method": "click"}
>>> {"params": {"text": "windmill", "id": "ysearchinput"}, "method":  
>>> "type"}
>>>
>>> (I had other methods after the 'type' but they require the search  
>>> query
>>> list to be populated).
>>>
>>> I've tried both the subversion and released versions of Windmill w/o
>>> success.
>>>
>>> Can anyone shed some light on this issue?
>>>
>>> Robert
>>>
>>> PS IIRC the last time I tried Selenium (which was some months ago)  
>>> it
>>> had a similar problem.
>>> _______________________________________________
>>> Windmill-dev mailing list
>>> Windmill-dev at osafoundation.org
>>> http://lists.osafoundation.org/mailman/listinfo/windmill-dev
>>
>> _______________________________________________
>> Windmill-dev mailing list
>> Windmill-dev at osafoundation.org
>> http://lists.osafoundation.org/mailman/listinfo/windmill-dev
>
> _______________________________________________
> Windmill-dev mailing list
> Windmill-dev at osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/windmill-dev