christiank
Occasional Contributor
Joined 10 years ago
User Profile
User Widgets
Contributions
Re: Log is not visible in testcomplete
Most likely this reason: The tested application crashed and test complete cant handle that, meaning the Runner is still trying to execute the test but cant (it just sits their). After a while the pc gets turned off (again windows task). Testcomplete does not get the chance to fully write the log. Why the Runner can not continue after this application crash I dont know.1.1KViews0likes1CommentLog is not visible in testcomplete
Hi, im using Testcomplete 11. Several times recently, unfortunately not reliably reproducable, Testcomplete will not show the log of a testrun. The test is executed at night using windows sceduled tasks and a batch script to launch testcomplete. The test has been run (I get emails from the test) but it will not show up in the logs in testcomplete itsself. However when I browse to the location on the harddrive where logs are located, there is a folder created for that testrun (time & date are correct). The difference to logs which do show in testcomplete is, that there is no file RootLogData.dat. Has anyone ever encountered this issue? Thanks, Christian1.1KViews0likes2CommentsRe: Runner.Stop(true) clears variables and ignores further breakpoints
Hello, I do have exactly the same problem. It seems to me like the Runner object holds all references to variables and breakpoints. And when calling Runner.Stop this object gets disposed and a new Runner object is created which starts with the next test item in queue, but has no idea of any variables or breakpoints. I did not yet check this with Project variables, just with a global script unit which holds the information I need throughout the tests. Kind of makes me feel like my test architecture is not correct, because like this the Runner.Stop method is completely unusable. Anyone else having any experience with this? Regards, Christian. EDIT: Project Variables do in fact keep their value after a call of Runner.Stop (true)1.1KViews0likes1CommentRe: Enable/Disable Test Items via Code
Hi, how about using Runner["Stop"](true) to work around this. Instead of activating / deactivating testitems according to certain conditions, have each testitem check its own run condition. If the condition does not match, ask the Runner to stop execution of this test item, but continue with the next one. function runTestItem2 () { if (Sys["UserName"] == "LazyTester") { Runner["Stop"](true) } else { doTheWork (); } } Regards, Christian. *Edit: Using this method will also skip over all ChildTestItems of the TestItem in which you execute this command.1.5KViews0likes3CommentsWaitWindow Parameters Optional & Required
Hi, we are using the WaitWindow method in our project quite alot. The help documentation for WaitWindow explains four paramters, two of them required and two of them optional. WndClass [in] Required String WndCaption [in] Optional String Default value: * GroupIndex [in] Optional Integer Default value: -1 WaitTime [in] Required Integer Result Object Coming from dotnet this is not clear to me, since optional paramters can only be used as last parameters for a method. How exaclty does TC execute this method when it is called like this (as we do in our project): ["WaitWindow"] ("xyz", "abc", 1) There will be no error on execution but to me this doesnt make sense. You could of course argue to not use the function like this but since Im newly assigned to this project and the is method is used quite extensively Id rather not change every single usage. We are using Version 10.40.2015.7534Views0likes0Comments