agabriel
Contributor
Joined 13 years ago
User Profile
User Widgets
Contributions
Re: How can I change ProjectSuite.Variables when using testexecute?
I was able to get around this problem by creating a Userform that would appear at the the beginning of the project run with all the fields that would have to be set and an OK and Cancel button. Once the user enters in the variables, they click OK and the values are saved as ProjectSuite variables for the duration of the test run. I even went a little bit farther and setup field validation and a networked lookup that will login to a database environment and let them select a database to test on. By default, the Userforms don't show when you create a new project, you have to right-click on the 'Advanced' folder in your project and add 'Userforms'. It will appear along with the default 'Scripts' and 'Events'.1.5KViews0likes0CommentsRe: Does Test Complete support Windows Embedded Compact (Win CE 7)
I've started an idea thread to get this going... http://community.smartbear.com/t5/TestComplete-Feature-Requests/TestComplete-Execute-Support-for-Windows-CE-Embedded-Compact-7/idi-p/99041 Please vote it up the line so we can get this into development already!874Views1like0CommentsRe: Windows CE support?
Hey everyone, If you're still interested in getting support for Windows CE, I've started the idea thread based on Tanya's suggestion. http://community.smartbear.com/t5/TestComplete-Feature-Requests/TestComplete-Execute-Support-for-Windows-CE-Embedded-Compact-7/idi-p/99041 Vote it up the line so we can get them on this!2.1KViews1like0CommentsTestComplete/Execute Support for Windows CE/Embedded Compact 7
This has been an ongoing request... http://community.smartbear.com/t5/Mobile-Application-Testing/Windows-CE-support/td-p/79621/highlight/true/page/2. that will find SmartBear A LOT of new customers and make some existing ones really happy. I understand the need to support iOS and Android testing with the hot new mobile market, but what about all of the mobile systems that existed before the Smartphone? They all run on a flavour of Windows CE; now Windows Embedded Compact 7.Re: The window was destroyed during method execution.
I've solved this issue via a different means. I did not want to just hide the log entry but actually prevent the problem from occurring. Some experimentation and I found that adding a delay would in some cases provide enough time for the window to 'recreate' itself...the problem is that there is no finite delay time that worked reliably. So my solution was to create a function that would wait until the object is visible before interating with it. The function: function WaitFor(_propertyNames ,_propertyValues) { var PN = _propertyNames; var PV = _propertyValues; var Depth = 1000; var Refresh = true; Log.Message("Waiting for Property '"+PN+"' and '"+PV+"' to become visible..."); while(!Aliases.BrowserWindow.Find(PN, PV, Depth, Refresh).Visible){ //Wait until the object is visible before proceeding } Log.Message("Property is visible"); } To use it, I just call on the function immediately before the action I want to perform: var PropNames = new Array ("propertyname1", "propertyname2"); var PropValues = new Array ("propertyvalue1", "propertyvalue2"); WaitFor(PropNames, PropValues); Aliases.BrowserWindow.Find(PropNames, PropValues, 1000, True).Click();2.7KViews2likes0CommentsRe: What does the "error generating the type library" mean?
Ping! I still get this error on occassion and I also get it in TestExecute but I can't pinpoint what is causing it. When I click the 'OK' button on that message, another message always appears that reads: Unable to create an Event Control instance. Make sure that TestComplete 9 is installed correctly and the testComplete service is running.1.6KViews0likes0CommentsRe: Testcomplete 9: Extremely slow test execution
This may help some others out ... I went from using a old machine (Dual Core - 4Gb RAM) to a newer one (Core i7 - 16Gb RAM), both on Win7, and saw a dramatic DECREASE in performance (ie. a test that took a few seconds now took 4 mins). In my case, the problem was corrected by changing 2 things: 1. I was using Performance Indicators that named the old machine. Changing them to the current system made the difference. 2. I changed the CLR Briding to 'same as OS' and enabled Multi-Threading. My tests started to run at optimal speeds for the machine that I am now using. My tests now run exactly twice as fast! I hope that helps at least one person!2.1KViews3likes0Comments