joe_2
Contributor
User Profile
User Widgets
Contributions
Re: Figure out if a Keyword Test is used
You could rename it instead of deleting. Or remove it instead of deleting, so its out of the project but still exists as a file. Then just operate as normal. If you don't get a runtime error then after a while you'll know that nothing references it and it can be deleted. If you do get the runtime error, then you know you need to restore it because it's still used. I never delete anything but test logs. And then I only delete the ones that I ran while developing my scripts. Not the 'for-the-record' test runs. For scripts and tests, I just remove them and then after a while put them in an archive folder. Who knows when you'll need something back that you discarded three years ago? 90% of all papers that get filed are never looked at again for any reason. That other 10% could bite you in the end, though, if you didn't file them.1.3KViews0likes1CommentRe: How to check if application is closed
VBScript snippet: <command to close the app here> Do While Sys.WaitProcess("ApplicationName", 1000).Exists = True Delay(1000,"Waiting for the application to close") Loop <commands for whatever comes next here> When it finishes that loop, the application is closed. If you feel the need, you can add a counter to the loop, and declare an error if it gets too big, to detect a hung app at shutdown. As-is, though, this will just sit there looping until it doesn't detect the application, then it will exit the loop. Each time through the loop lasts a second, approximately.3.5KViews0likes0CommentsRe: Test Complete cant see the right clicked menu
You open the popup menu with a right click, but you don't need to hover and wait for the submenu in order to click its item. You need to put both the popup menu and the submenu in your click call... Instead of Call ...Click("Change To...") Call ... Click("User Defined") You need Call ...Click("Change To...|User Defined") Trying to do it separately doesn't work because the popup closes as soon as the first click command runs.1.9KViews0likes0CommentsRe: Catastrophic failures when attempting Log.AppendFolder("message")
Trying to think of things I might have changed, I remembered that I had recently turned on several performance monitors, just to see if they would be useful. I never did make much use of that information, and so I turned them back off. The crash has not happened again since I turned them off. I'm going to tentatively say that something in the performance monitors was causing the problem, and move on. It's not a solution/answer, but it'll do so long as I can continue testing.1.3KViews0likes0CommentsRe: Catastrophic failures when attempting Log.AppendFolder("message")
This is not happening when it tries to write the log file, at the end of the script run. It is happening at random while the script is running, and more often right at the beginning of script execution. It happens when the following subroutine tries to run (VBScript) The subroutine is called an average of 10 times per script test, and I'm running about 30 script tests per test session Sub PushLog (StepDescription) Log.AppendFolder(stepDescription) Indicator.PushText(stepDescription) End Sub I've been using this subroutine to organize my test logs since before version 10 was released. Only started getting the crashes in the last week or so. It does not always crash, but when it does, it always crashes on the line to append a log folder. There is also a PopLog subroutine that is paired with the PushLog routine Together, they are used to improve readability of my test logs, and to post relevant messages to the progress indicator. I just wanted to know if others are seeing failures when trying to append a log folder, or if it's just me. I'm trying to decide if I need to reinstall TestComplete.1.3KViews0likes1CommentCatastrophic failures when attempting Log.AppendFolder("message")
I'm running version 10.20.953.7 I've suddenly started getting catastrophic failures (so far they seem to hit randomly) when attempting to: Log.AppendFolder(messageVariable) My scripts are VBScript and this line is in a two line function that just appends a log folder and pushes the indicator text when it is called. When it happens, I click the 'Ok' button on the warning popup, and TestComplete closes the popup. The test status indicator now indicates that the test is still running, but no more test actions are taken. Trying to stop the test changes the indicator to say that it is stopping, but it never finishes stopping. The only way to actually make it stop is to use task manager to forcibly shut down TestComplete. Anyone else seeing this? Is it related to a recent Windows update or something? Or have I corrupted something in my installation of TestComplete?Solved1.4KViews0likes3CommentsRe: Move a variable between two project suites
Yeah, when I was first learning how to use TestComplete, I made heavy use of external data storages. But I found they were somewhat unreliable. Occasionally a test would fail for inability to open a file, for one reason or another. Usually because the file in question had been moved by someone else... So I did away with them in my projects. Just use table variables now, and that's generally not a problem, except I started a new suite and needed a few of the old tables in it. What I wish is that SmartBear would make the project variables and suite variables copy and paste-able. Just right click a suite variable and copy it, then paste it into the other suite. Now I'd find that useful.1.4KViews0likes0CommentsRe: Move a variable between two project suites
Thanks for the response. I tried that. Got it to export to excel just fine, but when I tried to build the table variable, it put the values in the temporary portion of the table, didn't set the defaults. I couldn't figure out how to set the defaults, which meant I would need to either use a persistent variable (and it would have been the only one in the project -- I don't like exceptions.) or I'd need to re-fill it from the excel file each run. This is what I was doing a while back, and I found external data storages to be unreliable and hard to work with. What I ended up doing was rewriting the little subroutine I had made that exports it to the text file so that it would save a column of values instead of a comma delimited string. Then I used the data generator's 'values from a set' to import the values from the text file one column at a time. Clunky and roundabout, or what I like to call sledge-hammer programming. Figuring it out probably took about as long as re-typing the whole table would have. But I finally had the default values set in the new project suite variable, like I wanted, without having to re-enter all the data. And now I know how to move a variable between suites, in case I ever need to do it again.1.4KViews0likes2CommentsMove a variable between two project suites
I have two project suites. One of the project suites has a rather large table variable that I use as a lookup for specific x/y values to be clicked during a test. I'd like to duplicate the default values for this table in the other suite. Is there some way to export a table variable's contents, and then import it into another suite? I did manage to produce a comma delimited text file from my original table, but when I try to fill the empty table with that, it wants to put all the data into the first cell. I can use the split method in a script to make a temporary table full of the values, but don't know any scripting way of setting the default values in my target table... I'm beating my head against the wall, here, trying to move this stupid table without re-entering all the data. Any suggestions?1.5KViews0likes4Comments