[Gnash-commit] [bug #37223] JavaScript call didn't reach the ExternalInterface callback

[Nutchanon Wetchasit]

Follow-up Comment #7, bug #37223 (project gnash):

As for testing, the thing is, what is a proper way to test ExternalInterface?
ActionScript-only test cases (like ones I saw in `testsuite/misc-mtasc.all`
<http://git.savannah.gnu.org/cgit/gnash.git/tree/testsuite/misc-mtasc.all?id=6b269f9f3d518ca5372aa12876ca09be0743bac9>)
won't cut it, since this involves browser-Gnash interaction.

An alternative would be writing some (shell or Perl) script that fakes
Gnash's host container (run gnash with`--fd` option), and verify result
from both side. I haven't looked closely on this method yet.
Any suggestion?

By the way, these are list of simple tests I planned to write:

* Registered callback invocation test: ExternalInterface callback (pass) V.S.
_root callback (fail), aka. an automated version of js2flash-rootcb test.
* Registration test with `method=null` and `method=undefined`: callback
registration must fail to pass.
* Registration test with `instance=null`: callback registration should succeed
to pass.
* Test on `this` inside callback when `instance!=null`: user-specified Object
(pass) V.S. registering code's `this` (fail) V.S. Function's class (fail) V.S.
_root (fail).
* Test on `this` inside callback when `instance=null`: must be an empty value
(`null` or `undefined`) and instance variable reference must give `undefined`
to pass.
* Test on `this` inside callback when `instance=null`: must give `undefined`
to pass. (This one is expected to fail)
* Long callback arguments test
("The","quick","brown","fox","jumps","over","the","lazy","dog"): must be
passed correctly to pass.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?37223>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/