stein_oddvar_ra
Contributor
Joined 11 years ago
User Profile
User Widgets
Contributions
Getting an on-premise license for TestExecute is always slow, and sometimes fails
Hi, Recently we have moved from getting licenses from a HASP-license server to the new SmartBear Licensing Management (SLM) solution. We have upgraded our TestComplete/TestExecute installations to 15.55 and setup an on-premise license server that server licenses to the clients. All clients have been setup with the URL for the SLM-license server. We experience that getting a license from the SLM-server takes much longer than with the previous HASP-solution. Sometimes the license acquisition fails, with the message: "The user did not log in using the SmartBear account or did not pass the accesskey in the command-line arguments. TestComplete will be closed.The user did not log in using the SmartBear account or did not pass the accesskey in the command-line arguments. TestComplete will be closed." What can I do to ensure that our licenses are served efficiently and reliably to our TestExecute-clients?316Views0likes1CommentRe: Deleting added TestedApps shows strange behaviour in python
Hi, ebarbera Yes it does. I use the TestedApps.Count value to set the number of times to iterate. The code is simple: def del_applications(): # Deletes all applications from the TestedApps numApps = TestedApps.Count Log.Message(f"Deleting {numApps} apps from TestedApps.") for i in range(numApps): if not TestedApps.Delete(i): Log.Warning(f"Could not delete app index {i} from TestedApps") It logs the correct number of apps, but deletes only the first half of them. The rest fails. The bug is present in TestComplete 15.10.445.7542Views0likes0CommentsDeleting added TestedApps shows strange behaviour in python
Hi, I've just noticed something odd. Our test application is adding a list of TestedApps for use and to be sure no apps are added twice, we purge all existing TestedApps first. This works when we're using JScript or CScript like this: function del_applications() { // Delete all TestedApps var count = TestedApps["Count"]; for(var i = 0; i < count ; i++) { TestedApps["Delete"](0); } } Using Pyhon however gives a strange behaviour. This is the python script: def del_applications(): # Deletes all TestedApps count = TestedApps.Count for i in range(count): TestedApps.Delete(i) The python script deletes exactly half of the applications, then the next time I run it, it deletes half of the remaining applications. I can do this until eventually I have deleted all the applications in TestedApps. I'm using TestComplete 14.91.341.7 x64 on Windows 10 Standard, 64-bit (10.0 Build 17763)725Views0likes6CommentsRe: "Server not started" error on master after successfull tests
Hi, Thank you for the suggestion. The "Verification failed" is not relevant. When I try to verify the slave, the verification succeeds. When I try to run tests, the slave runs one or two tests, then stop. On the master, the error "Server not started" can be found. I will contact support.1.8KViews1like0Comments"Server not started" error on master after successfull tests
Hi, We have started to get problems with our tests on one of our setups. Or setups consists of two slaves (running TestExecute) connected to a master (running TestComplete), and the tests are running in sequence on the slaves. One of these setups has now started to fail: One of the slaves runs all the tests, but the other stops after running only a few of the tests (two or three tests). The log on the master says "Server not started", and the log of the successful test on the slave does not contain any failures. I can successfully verify the failing slave from the master project, and ping, remote desktop and windows file sharing works both ways. Host OS: Windows 10 Enterprise 2019 LTSB Build 1809 TC: 14.40.1658.7 x64 TE: 14.40.1658.11 x64Solved1.9KViews0likes4CommentsRe: "Server not started" error on master after successfull tests
There is nothing unusual in the logs on the failing slave. We can open the log of the last test that ran, and there is nothing there that indicates any problem. The next test is never started. The only error we get is on the master - the "Server not started" error.1.8KViews0likes0CommentsAutomatic minidump to include heap
TestComplete saves a minidump of an executable that crashes on the PC it is running. These programs could crash due to the testing being performed, and the minidumps are very valuable when analyzing the test results. It should be possible to incude the heap to the minidump. Either by default or as a configurable option.