#12 new
hosiawak

Failing Autocompleter/InPlaceEditor unit tests

Reported by hosiawak | May 22nd, 2008 @ 11:39 PM

Ajax.Autocompleter and Ajax.InPlaceEditor unit tests are failing in FF 2.0.0.14.

Autocompleter failures:

testAjaxAutocompleter

7 assertions, 1 failures, 1 errors

Failure: 'ac_update' was not visible. undefined

TypeError: $("ac_update").firstChild has no properties(TypeError: $("ac_update").firstChild has no properties)

testAfterUpdateElement

2 assertions, 2 failures, 0 errors

Failure: 'ac2_update' was not visible. undefined

Failure: assertEqual: expected "'afterupdate:LI'", actual "'abcdefg'"

testTokenizing

1 assertions, 3 failures, 0 errors

Failure: assertEqual: expected "'test1'", actual "'abc'"

Failure: assertEqual: expected "'test1,test2'", actual "'abc,abc'"

Failure: assertEqual: expected "'test3,test2'", actual "'test1b,test2'"

testAjaxAutocompleterNoLinebreaksInResult

7 assertions, 1 failures, 1 errors

Failure: 'ac_update_br' was not visible. undefined

TypeError: $("ac_update_br").firstChild has no properties(TypeError: $("ac_update_br").firstChild has no properties)

InPlaceEditor test:

testControlOptions

45 assertions, 8 failures, 0 errors

Failure: Not just one submit: expected "1", actual "2"

Failure: There should be no submit: expected "0", actual "1"

Failure: There should be no submit: expected "0", actual "2"

Failure: There should be no submit: expected "0", actual "2"

Failure: Too many nodes in the form.: expected "1", actual "3"

Failure: Too many nodes in the form.: expected "1", actual "3"

Failure: The form should have only two nodes (edit+cancel): expected "2", actual "3"

Failure: Incorrect nodes: expected ['input', 'a'], actual ['input', 'input', 'a']

They're failing because keypress event (trigger) was changed to keydown (possibly for IE/Safari compatibility).

I'm not sure whether we should update the testing framework so that it reacts to keydown or fix Autocompleter/InPlaceEditor ?

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป

script.aculo.us is an open-source JavaScript framework for visual effects and interface behaviours.
<br/><b>Source available from github</b>
The Git repository resides at:
<a href="http://github.com/madrobby/scriptaculous">http://github.com/madrobby/scriptaculous</a>
<br/>Check out the current development trunk with:
<code>git clone git://github.com/madrobby/scriptaculous.git</code>
<br/>As <b>script.aculo.us 1.xx is feature-frozen</b>, this development trunk is for <b>bugfixes only</b>.
<br/>New development should happen only for
<b>script.aculo.us 2</b>.
<br/><b>Creating a bug report</b>
When creating a bug report, be sure to include as much relevant information as possible. Post a an example that shows off the problem. Preferably, <b>alter the unit tests</b> and show through either changed or added tests how the expected behavior is not occuring.

People watching this ticket

Pages