Contributions
Error message when running a test with parameter in command line
It seems that this problem occured after upgrading to TestComplete 10.20, it worked well on 10.10. I run a KeywordTest via command line like this: %TC_PATH% %SOLUTION_PATH% /r /p:AV_Studio_Tests /t:"KeywordTests|PerformanceTest_Main" /e PerformanceTest_Main uses a parameter which is set to default value, so I assume i shouln't need to specify it once again in command line. It used to work fine this way, but now (on 10.20) I got this error message. Is there a way to turn off this error message? (I really wouldn't like to waste my time and downgrade to 10.10)1.4KViews0likes1CommentTest execution is stuck on "The window was destroyed during method execution."
Hello, I've been trying to automate a test case, in which the application under test may get hung - if it gets hung I'd like to killl the process and restart the application to proceed with further tests. The only problem is that I'm not able to tell if its hung or not (in order to decide whether the process should be killed). First I thought that after performing the operations which may cause the application to hang, I'd try to close some opened modal window and check if I can perform some new actions on the application - If they succeed it means everything is fine, if not it indicates that the application is hang. The problem is that, when appliation is hang, trying to close this window causes TestComplete to stuck at the line calling the Close() function, stopping TestComplete manually doesn't help (it's in the "Stopping" state all the time), I have to kill the application under test process manually to be able to stop the tests. In the log I receive this message "The window was destroyed during method execution." (it corresponds to the line where I tried to close a modal window). What I'd like to accomplish is to be able to decide in the tests whether the application is hung and I should kill the process or it's fine and I can proceed with further tests. Can you advice me a proper way to overcome this problem? Is there maybe a way to set a timeout, after which TestComplete will proceed to further steps if the window, on which it is trying to perfrom some actions, was destroyed.12KViews0likes2CommentsTE time-limited license expired problem, although we have a permanent one
Hello, every while (like once a week, most of the time it works fine) I got this "Your time-limited license has expired." message box on the machine, where TestExecute is installed (please see the screen shot below). The tests are run automatically every night, so it's annoying when in the morning I see this message box instead of test report (as it makes it impossible to continue tests execution). When I close the message box and re-run the tests solution manually, it works fine (please note that also when run automatically overnight, most of the time it works fine, but the problem happens quite regularly). Of course we have bought the permanent license for TestExecute. What might be the cause of this problem?18KViews0likes1CommentLarge log files (already disabled Visualizer)
Hello there. I've been wondering why the logs exported to .mht files take so much disc space? Usually out tests last about 2 hours and the log files are 10-40 MB (that is already way too much in my opinion). Last night the tests went for about 7 hours and the report file couldn't be sent via e-mail because it was 2 GB large after zipping. I already disabled Visualizer in our tests. What can I do to minimize the log files size? Is it normal that they take so much space? Is there any other way to export the log files? (so they don't take so much space)23KViews0likes0CommentsDragging and dropping doesn't work reliably
Hello there. I do a lot of drag and drop in our application under test so I'v created a function which drags an object from one position and drops it somewhere else. Sub dragFromTo(start_x, start_y, end_x, end_y) Call LLPlayer.MouseDown(MK_LBUTTON, start_x, start_y, 200) Call LLPlayer.MouseMove(end_x, end_y, 400) Call LLPlayer.MouseUp(MK_LBUTTON, end_x, end_y, 400) End Sub But the problem is, this doesn't work reliably - the tests which include drag&drop operations may pass right after creating them, but sooner or later during playback there are fails because drag&drop operation didn't work properly (by not working properly I mean that the thing was actually dragged, I can see it on the screen, but after dropping it wasn't added to the new position, as if you dragged and dropped a file into a folder but it wasn't actually in this folder after dropping). I calculate the coordinates dynamically with objects bounds. Do you have an idea what may be the the problem in this case, perhaps the timing? Is there any way to make the drag&drop any more reliable than the function above (having given the coordinates of the start and end point of the drag&drop operation) ?22KViews0likes2CommentsAutomatic reports via e-mail only on errors
I've been wondering if there is a good way to automatically send e-mails with reports generated by TestComplete only if any test in project failed (for example with 'Some tests failed' subject to distinguish them). If all tests passed, just a notification about successful execution would be enough (no report attached, 'All tests passed'). I've browsed through the resources about raporting/e-mails but couldn't actually find a solution which suits the scenerio above, can you think of some good way to do this?21KViews0likes1Comment