Contributions
Start of powershell on 64bit (windows server 2016) environment leads to an error
Hi, I have a problem with starting of powershell out of my script. I need to start a powerhell script out of a function: var obj_Shell = Sys.OleObject("WScript.Shell") obj_Shell.Run("C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\powershell.exe -NoExit") The shell starts with the following error: You are running PowerShell in 32bit console. This may lead to compatibility issues! please use only 64bit PowerShell console! If I use "obj_Shell.Run("C:\\Windows\\SysWOW64\\WindowsPowerShell\\v1.0\\powershell.exe -NoExit")" I get the same error. I don't understand the problem. I use TC 12.60 Can anybody help?795Views0likes2CommentsRe: NameMapping File and Git Source Control
Marsha_R Thats the point, the maintanace (in my case) is much lower than using NameMapping. We had more than 1000 mapped object in our NameMapping. Becasue the tested application was still in development we spent some days to find our objects again (structures changed, controls renamed and so on). Now with the 'find' (we implmeneted some logic to be able to use this function for our purpose) its's much easier. Why- We can dynamicaly search for objects based on only a few 'base objects'(and their informations) and for example passolo- files which are provided by the developers (we do not need to change any properties). If a structure chages I have only few points where i have to adjust to make it working again2.6KViews0likes0CommentsRe: Requesting a feature to run only the failed test items in the project suite
We have solved the problem by writung a flat file with the result of each testcase (testiem). After rhe testrun we create (with powershell) a new .mds with only the testcases (testitems) which failed. Then we restart it automaticaly.1.7KViews0likes0CommentsRe: NameMapping File and Git Source Control
We were facing the same problem. As a result we did not use the name mapping. We use the 'find method' instead what makes the mapping much easier and even more maintainable. We have different scripts where we maintain the paths to the objects.2.6KViews0likes2CommentsRe: Long time goes by between Runner.Stop(true) and the start of next testitem
I have tried a workaround. Each testcase is capsulated by a try- catch block. Instead of using the "Runner.Stop(true)" code I throw an error with a defined message and code. Then the catch block is entered. Within the LogError- Event I check for the exception- text that I have defined. If it matches I set my testcase to true (a function that I have to be able to log in to a flat file) and no error is through. Now I have no delay between the execution between stop and start.1.3KViews1like2CommentsLong time goes by between Runner.Stop(true) and the start of next testitem
Hi all, For my project I use the scripting- approach (JScript). My testcases are capsulated in testitems. The complete Project has around 400 testitems. Some of the testitems have not be be executed (for example based on countries). I use the "OnStartTest" and "OnStopTest" events. Before a testitem starts it loads it's configuration (for example country settings, users and so on). Based on these informations the script starts a simple check if the testcase is allowed to be executed. If the testcase has not to be executed I use "Runner.Stop(true)". In the"OnStopTest" event some loggings are executed. So far so good. Now I see that the time between the stop of a testcase (stop- event was processed) and the start of the testcase (start- event) increaeases after each execution. That means that there are for example 10 testitems that must not be executed. After the first testitem it takes only around one second between the stop and the next start. After the second stop it takes more than 2 minutes. Than five .... after the 5th stop it takes around 30 minutes. I can also see, that the memory usage decreases after the stop- event. It seems that testcomplete starts to destroy some objects. So my question is if somebody else has the same problem or has a solution. P.S: If testitems are allowed to be executed it takes only one second between stop and start I use TC and TE 12.10 and 12.60, always the same behaviour1.4KViews0likes5Comments