kroe761
Contributor
Joined 11 years ago
User Profile
User Widgets
Contributions
Firefox auto-updated to 41.0.2, now tests won't run
I was running Firefox v41, and I used the most recent Firefox patches to make sure it was running correctly. This morning, it updated to 41.0.2 (don't know the original version, just know it was at least v41). This actually happened while I was running tests in FF. After the update, TC no longer can use FF. This is the first time I have seen TC not run on what was (presumably) and minor update, not an update from v40.x.x to v41.x.x. Has anyone else run across this problem? Thanks, KevinSolved3KViews0likes8CommentsRe: TC 11.1 and Chrome 45 test playback very slow?
@brk9394 Thanks for the info! I'm now activly trying to avoid contentText, and I was using it everywhere. The odd thing, though, is that until the update the performace was much better, including using contentTexts. But still, thanks! @TanyaGorbunova I was running the tests in a windows VM used solely for these tests. There were no extensions enabled.3.5KViews0likes1CommentTC 11.1 and Chrome 45 test playback very slow?
Ever since I upgraded to TC v11.1 and Chrome v45, my test performace has slowed drastically. I have three test projects, each running as a distributed network test in seperate VM's, all running in Chrome (internal business applications, programmed by the devs to run in Chrome). I ran one test in Chrome and it finished in 3:30 minutes, but in Firefox it ran it 1:11 minutes. Before the upgrade, a project that ran in about 1.5 hours now takes over 3, another one that used to take about 3 hours now runs in about 4.5 hours, and another one that took 2.5 hours now runs in over 8 hours. Fore the third one, a major chunk of the tests revolve around a Kendo UI grid. Now, for some weird reason, TC cannot find the columns button as shown here (http://screencast.com/t/cDhXmTum1a). This, however, does NOT work in Firefox. This used to work in v11.0 for Chrome. is anyone else experiencing issues like this? Thanks for your help!3.8KViews0likes10CommentsRe: Google has now removed npapi support from Chrome, what is SmartBear doing about Chrome support?
Good to hear about the TestComplete v11.1 update. I have two questions: Is there a direct link to the update that we can download? For some reason TestComplete cannot find the update, and since I am testing internal applications optimized solely for Chrome, I need to have this fixed. Also, has TestExecute been updated to v11.1 as well with Chrome 45 support? Thanks!2.8KViews0likes1CommentDistributed testing: Cannot load the remote project. Failed to invoke an object. Reason: timeout ex
Very weird question, and this issue just started yesterday, with seemingly nothing causing it. I have run several distributed tests every night. They are ran from a virtual machine called QA-MASTER and the tests are sent to several slave machines (QA-1, QA-2, etc). If I run the tests as my local machine as the master and sending the tests to QA-1, it works correctly. However, when I run the tests from QA-MASTER using the exact same code (code is from an SVN repo, so it's the same code) I receive the messages for each test "Cannot load the remote project. Failed to invoke an object. Reason: timeout expired" and "Cannot close the remote instance of TestComplete(TestExecute). Object disconnected" (see screenshot: http://screencast.com/t/0VW41pcx). Both TC on the master computer(s) and TE opn the slave computers are on 10.60 and when I verify the QA-1 on the hosts page it succeeds. Not only that, but I can even copy the project files to the remote slave. This is causing serious issues because these tests need to be run every day. I can run them locally, but obviously I cannot work during that time because it locks up TC. Thanks very much!1.3KViews0likes1CommentDistributed Testing - Test Execute never moves on to 2nd test if 1st test is too long???
Background - My Project suite has multiple projects, each is ONLY ran in a distributed setup. The Project is ran every night on a Master VM using TestExecute. The Network Project contains 4 tests: 1: Job One / Task One - deploys to a VM to test in Chrome Project One) 2: Job Two / Task Two - deploys to a VM to test in Chrome (Project Two) 3: Job Three / Job Three - The job contains two tasks, deploys to separate VM's to test customer-facing site in different browsers (Project Three 4: Script / Send Email - script under Network Project that saves the test log and emails it to various business owners (Network Project / Advanced / Script) The problem: The first test under the Network Project can be quite long, sometimes taking up to three hours. After it finishes (I receive an email when it finishes via a script) it never moves on to the 2nd job, but just hangs indefinitely. However, if I disable all but a few of the tests within the Project One, thus greatly reducing the time Network Project Test One takes to run, it moves on to Network Project Test Two with no problem. I don't understand why that would happen. I have one test within Project One that fails every night, but it moves on to the other with no problems; also, if I manually force one of the tests to fail during short run as described above, the Network Project still moves on to the next test/job. No to mention that I also have failures in Test 2, and Test 3 doesn't fail to start. If there was a setting somewhere that I needed to change (a "if test takes longer than 2 hours" setting, something like that), I would have expected TE to close after a time instead of just hanging. I come back into the office in the morning and TE still says "Running" in the corner, but it's not doing anything. I could probably turn all of the tests into tasks under 1 job, thus they will all run in parallel. But then TE will just hang and never execute the Send Email test, and since I want it to run after everything has finished that won’t really work. Also, each task is set up Action After Run=Log off from computer and UsePrevious Instance=Restart TestComplete. Don't know if that is relevant or not, but it feels like it. Any help would be greatly appreciated. Thanks!!!How to tell TestExecute to use saved RDP settings?
I am using Test Execute to run distributed testing over several different VM's. The problem is that one internal web applicatoin we use has to be used at 1920x1080 resolution, and it doesn't seem test execite is smart enough to scroll to the left and right like it can scroll up and down. So I need to find a way to tell TestExecute (coded via Test Complete) to open an RDP session using saved settings that include smart sizing:i:1 (http://support.smartbear.com/viewarticle/56548/). The works manually, but how can I open that RDP session when test Execute is started via command line? Thanks very much!Test Execute: "Network error. Probably, the remote application has been terminated."
I have a set of VM's with Test Execute that I use distributed testing on. The master VM executes a distributed testing project and sends the tests to other VM's to run on multiple browsers. Lately, I have been executing the tests on the master VM, and then opening the slave VM in RDC and watching the tests execute (nice to see them running). After the tests are over, I see the log files appear in IE on the slave machine, but TE keeps running (as indicated by the pause/stop button on the upper right corner) on the master VM. After some time, I click the Stop button, and the log file that appears on the master VM says "Network error. Probably, the remote application has been terminated." What's going on here? I expected A) TE to exit when the tests stop (as I saw them run) and B) the test log files to appear after that on the master VM, not the slave. Thanks!764Views0likes1Comment