cannot run Sys. commands from my machine

Hi,



You recorded your script with automatic Name Mapping. To make TC record your actions without it, uncheck the Map object names automatically setting, open the NameMapping project item and clear its contents.

The Sys script was not recorded by anybody, it was from a code example in the Testcomplete Help. Shouldn't we be able to use both our recorded code and system specific scripts at the same time?



Robert

If name mapping is present for a Sys based object/application, etc., TestComplete expects you to use the name mapping.



So, on your machine, you have certain things mapped in name mapping including the Sys object.



On your co-workers machines, they do not.



This is the cause of the difference.  The help file sample scripts are very generic and, as far as I can tell, are only meant to demonstrate techniques.  Changes in environment, in code structure, etc., may make sample scripts work differently for different people.

But we are using the same project from a repository and he has name mapping enabled on his just like mine. But the Sys script works on his but not mine. Our properties and options are set the same so shouldn't the project act the same on both machines?

Curious indeed.



I noticed their code is using a "FindChild" call but you're using an Alias call.  They don't seem to be doing the same thing, actually.  FindChild will return the object just like Aliasing does but usage of "FindChild" should be to find an object, assign it to a variable, and then use that object to do something else.  Aliasing IS the assignment itself.  So, it seems that there's something different in the usage between what you're doing and what they are doing.  To investigate:

1. Are there specific error messages you get?  What's the behavior that's happening on your machine when you use the Sys.Process call?


2. Could you post the whole context of the script code that you're using versus the script code they are using?  


3. Also, are there different operating systems between your machine and theirs?  What is the mapping criteria set up in your Alias definition?

I apologies I was wrong. He did not get it from the help but from another post on here. http://smartbear.com/forums/forum/post/?mode=singleThread&thread=c8180fd1-d3bf-4b4b-9495-0a9e28bb1fd8    the following is the actual script we are trying to use.



var applicationName = "CALCit x64";

    var bCaption = "Uninstall*";

    var WshShell = new ActiveXObject("WScript.Shell");

    var oExec = WshShell.Exec("RunDll32.exe shell32.dll," + "Control_RunDLL appwiz.cpl,,0");

    Delay(2000); 

    Sys.Process("Explorer").Refresh(); 

    //var wnd = Sys.Process("Explorer").FindChild("WndCaption", "Programs and Features"); 



var wnd = Aliases.Explorer.wndCabinetWClass.ShellTabWindowClass.DUIViewWndClassName.DirectUIHWND.CtrlNotifySink.ShellView.FolderView;



if (!wnd.Exists)

    {

        Log.Error("The 'Programs and Features' window was not found");

    }

       



We have identical machines with the same processor, ram O.S. everything. He can run the code that is commented out above but when I uncomment it and comment the Aliases out it bombs. We have checked our options in testcomplete and they seem to be set the same. We are asigning the FindChild to a var and then use it.



If I uncomment the var wnd=Sys.Process line and comment the Aliases.Explorer line I get the following error.



The error log says: The 'Programs and Features' window was not found



Also you will notice the first Sys.Process("Explorer").Refresh(); is not commented out and Testcomplete does not compolain about it, just the next line.



I do not know what you mean by mapping criteria set up in your Alias definition.

Just another example is when he uses the //aqFileSystem.DeleteFolder("C:\\Users\\" + Sys.UserName + "\\AppData\\Local\\Flow-Cal, Inc\\CALCit\*", true); I have to use  aqFileSystem.DeleteFolder("C:\\Users\\robert.COASTAL\\AppData\\Local\\Flow-Cal, Inc\\CALCit\*", true); in order to acess the users info on my machine. Mine soes not like the Sys.UserName for some reason.

The code, as I read it, opens the Programs and Features window in Windows 7 using the WScript.Shell object to execute the command line.



So, what is supposed to happen is that the window opens and the FindChild call finds the object and passes the handle of it to wnd for use in the next line of scripts.



Are you and your two co-workers editing the same PROJECT out of the repository or are you just using the same library code routine?  It almost looks like they are set up for a "Flat" object tree and you're using a "Tree" object tree (a setting on the project level).



Something else:



As mentioned above, if you have NameMapping done at all, calling "Sys" by itself may be causing you issues.  Just as a test, compare the contents of the NameMapping node on your machine versus the NameMapping node on your co-workers machine.  Attached to this message is a screenshot showing an "Empty" NameMapping and one showing a NameMapping that has the Sys object mapped.  If yours is empty, we'll have to look elsewhere.  If you have the Sys object mapped, then you'll have to either remove the NameMapping object entirely from your project or you'll have to call NameMapping.Sys everywhere you want to use it.

Yes we use and edit the same project from a central repository. We both have the default Tree setting. I attached the screenshot of OUR Mapped Objects.

On a hunch (don't know if this will fix it), there's an environmental setting that is machine specific, not project level.



Go to Tools | Options | Engines | General.  There's a check flag that says "Use short names when possible".  Compare that setting between your machine and your co-workers' machines.  This SEEMS to be affecting the same stuff, but I can't be sure. 



Also, on the same lines, the option mentioned above for "Map object names automatically" is an environment level item and not a project level item.  That's found under Tools | Options | Engines | NameMapping.  Again, compare that setting among your machines.  



Beyond that, I'm not sure where else to look.  Perhaps an official SmartBear person might have a better idea of what to check if these ideas don't work.