Mock-as3 problem

Question

Hi,
Anyone using Mock-as3?  I am and am having a problem.  In a nutshell I created an interface so I could mock the flash ExternalInterface class.  I'm setting expectations prior to calling methods that invoke a mock object built on this interface.  Here's the test code:
         appState.openWindows.push("window1");
         var args:Array = ["window2"];
         mockExternalInterface.mock.method('available').andReturn(true).anyNumberOfTimes;
         mockExternalInterface.mock.method('call').once.withArgs('closeWindow', args);
//         mockExternalInterface.mock.method('closeWindow').withArgs('closeWindow', "window2").once;
         mockExternalInterface.mock.method('call').withArgs('closeMainWindow').once;
         var event:MenuEvent = new MenuEvent(MenuEvent.ITEM_CLICK);
         event.item = menu.menubarXML.menuitem.(@label == "LogoffAndExit");
         var myMainMenuEvent:MainMenuEvent = new MainMenuEvent(MainMenuEvent.CLICK);
         myMainMenuEvent.menuEvent = event;
         menu.menuHandler(myMainMenuEvent.menuEvent);
The call to mockExternalInterface.available is working.  I get a "No Expectation set" error for "MockExternalInterface.call(closeWindow,window2) From Mock-as3.  I've tried setting the expectation using both the String "window2" and the Array "args".  Note the "call" method signature - I suspect that this might be the core of the problem.
(Mock)ExternalInternalInterface.call(functionName:String, ...args);
Thanks,
Rich

Answer 1

I think I may have figured out the cause of the behavior I described below.  The  following article on the FUnit web site  describes a difference between JUnit and FlexUnit behavior WRT equality  comparisons on arrays.  Here's a short snippet from the  article:
The  intent of ‘assertEquals’ according to xUnit convention is to ensure that the  value of two objects are identical, not that they reference the same object. A second assertion type  ‘assertSame’ exists in JUnit (’areSame’ for NUnit) to ensure that two objects  share the same memory  reference.
This seems to explain what I was seeing so I did a quick test to see if this is what is going on in  mock-as3 as well  I changed my mock implementation to  store a reference to invocations of the ExternalInterface.call()  method:
public var callInvocations:Array =  new Array();
public function call(functionName:String, ...args):*
   callInvocations[callInvocationsCurrentIndex++] =  [functionName, args[0]];
   return null;
I then checked the results, first  using:
assertEquals(mockExternalInterface.callInvocations[0], ["closeWindow", "window2"]);
This failed with a message basically stating that "<closeWindow,window2> doesn't equal  <closeWindow,window2>", the same message I got from  mock-as3.
Then I changed the check to this:
assertEquals(mockExternalInterface.callInvocations[0][0], "closeWindow");
assertEquals(mockExternalInterface.callInvocations[0][1], "window2");
Now the test passes.  Hmmm, seems like this might explain things.  If true, then mock-as3 will never work correctly for functions that contain a "...rest" argument.  Now if I can only figure out how to contact the mock-as3 guys and let them know what I think I've found.
Hope this helps someone.
Cheers,
Rich