Michael_Colclou
Occasional Contributor
Joined 13 years ago
User Profile
User Widgets
Contributions
dotNET command to support .NET 6.0 and later
In the Test Complete help page on 'Calling Functions From .NET Assemblies' at https://support.smartbear.com/testcomplete/docs/testing-with/advanced/using-external-functions/calling-from-dotnet-assemblies.html it states: Calling functions from .NET assemblies is not supported for .NET Core and .NET 5.0 - 6.0 applications. This is a big gap in support. We are trying to move our application from running on .Net framework (4.72) to .NET 6.0, so all our assemblies will be built for .NET 6.0, meaning we can no longer call them from Test Complete. We use the dotNET command extensively in Test Complete. Our tests will not work without the dotNET command working with .NET 6.0 assemblies. I am sure this must be a problem for other Test Complete users, given that there is a big trend now to move to the newest .NET version and not be stuck on .NET framework which is now a legacy framework with performance problems.858Views5likes2CommentstchostingProcess.exe
Hi All I am occasionally seeing the following error in the test complete log from our suite of automated tests: Message: The tcHostingProcess.exe process crashed. 3:55:47 Normal D Detail: Exception code: 0xE0434352. Process identifier (PID): 7004. Dump file: tcHostingProcess_ue_8ee278e.dmp. This happens with just 1 or 2 of our > 1500 test cases, and even then only occasionally. This seems to happen when we call a method in one of our .net dlls via the CLR bridge mechanism. Has any one else had this problem? Are there any known issues in this area? Are there any suggested workarounds? We are using Test Complete 10.30.1145.7; was this a known bug in this version that is fixed in a later one? thanks Michael918Views0likes1CommentRe: Test Complete performance on Windows 8
More on this problem, in case any one else encounters it. It doesnt seem to be Windows 8 specific as I also have a Windows 7 machine that displays bad performance with test complete. However the Windows 8 machine is a lot worse. I also have a Windows 7 machine that displays perfectly acceptable performance, and I don't know what the difference between them is that would cause this. The problem also manifests itself in using the object browser. Expanding an item at the top level or the next level down is fine, but the level after that either doensnt expand at all or takes many minutes, making the object browser unusable. I have seen some other posts that report a similar problem The main conclusion though is that Test Complete 10.30 seems to fix all these problems. The performance is absolutely fine when I installed my trial version691Views0likes0CommentsTest Complete performance on Windows 8
Hi All Is there are performance problem on Windows 8 when playing back test complete scripts? I am using test complete 9.20 on both windows 7 and windows 8. Both machines are native machines with appproximately the same specification in terms of CPU and memory. I am running the same scripts against the same build of the software under test. On windows 7, 1252 tests complete in 7 hours 10 minutes On windows 8.1, 578 tests complete in 20 hours, after which a timeout occurs, so the remaining 674 are never run. It does not seem to be one specific test or set of tests that runs slowly, they all seem to suffer the same problem. For instance, one test takes 14 seconds on the windows 7 machine and 1 minute 33 seconds on the windows 8 machine. Is there a known issue with performance of test complete on windows 8? thanks Michael1.4KViews0likes2CommentsRunner.Stop(true) stops all tests, not just the current test
Hi I am using test complete 9 I have two simple tests: function test1() { Log.Message("Executing test1"); } function test2() { Log.Message("Executing test2"); } and a event handling function: var errorInStartTest = true; function GeneralEvents_OnStartTest(Sender) { if (errorInStartTest) { errorInStartTest = false; Log.Error("Error occurred in OnStartTest, calling Runner.Stop"); Runner.Stop(true); } I set up a project suite containing test1 and test2 I am expecting test1 to fail because an error occurs in the OnStartTest event but test2 to run successfully. The Runner.Stop(true) call should stop the execution of the current test: test1 and go onto the next test: test2 What actually happens is test1 run and reports an error but test2 is never executed. I use the Runner.Stop(true) call in other places and it does stop execution of the current test and go onto the next test, so why isnt it working in this case? Could it be because the call occurs in the OnStartTest event? thanks Michael7.8KViews0likes5CommentsScintilla support
Hi The application I am testing uses a code editing component from Scintilla (http://www.scintilla.org/). When I try to look at the properties of the Scintilla object within the test complete object browser it doesnt show anything and I am unable to work with it. Does Test Complete claim t support this component, and if not, could support be added? thanks Michael22KViews0likes1CommentRe: ODT from one Project used in another in the same suite
Hi My organisation too have a requirement to be able to share ODT data and classes across more than one project. Please could you further increase this features priority in your database. When can I get an indication of timescales for this feature? thanks Michael768Views0likes0Comments