Visual Studio Integration - Include Test Complete Tests as part of Visual Studio Load Tests
Visual Studio enterprise allows us to create Load Teststo performance test our application. This achieved by creating a series of Web Performance Test scripts and then creating a Load Test setup to distribute the scripts and user load in a controlled manner. (Fig 1) Currently Test Completes support integration with Visual Studio where Test complete scripts can be run via a Visual Studio controller and Test Agent config. But this is limited to only running Test complete tests one by one (Like a regression test suite). Unfortunately a Test Complete script which is in a Visual Studio project cannot be run via the Visual Studio Load Test setup as it does not recognise Test Complete scripts. You get the below error when tying to add the test to a load test config (Fig 2) The reason why Test Complete comes in handy for load tests is because some applications depend on processing in the client end before displaying the results in the GUI (something like a thick client). The time taken for this processing would not be captured via middle tier simulation supported by Visual Studio. Business critical systems which require transaction performance monitored release by release will benefit from the ability to include Test complete scripts in a Visual Studio Load Test as it will allow us to create background "Load" via Visual Studio scripts and monitor real life End to end transaction performance under load via a series of Test complete scripts which run as part of the load test.
Double-Monitor and Logging ...
Hello, I work with two monitors and after running Keywordtests the pictures in the log are showing the secound (for testing unused) monitor. It´s not necessary to make a picture of both screens and I think nobody uses two screens for testing. So pleasechange the process of screenshot making limited to one screen only or make it chooseable from which screen pictures are been taken. Attached Screenshot is showing my secound (blank) screen on the left side.
Support for FireMonkey / FireUI
TestComplete lacks support for testing of Delphi / C++Builder applications that are using the FireMonkey / FireUI cross platform framework.The only options are to use OCR or low-level mode tesing, making UI testing cumbersome. The FireMonkey framework is actually widely accepted and getting momentum in the Delphi community, and missing support for FireMonkey is quite a pity.
Suppress automatic description fill during recording of a keyword test (keep it blank).
After recording a keyword test, the first thing I do is blank out the description for every new line. Here's why: The concocted description gives no added value. You can look at the other three columns and figure things out easily. When I want to override the concocted description with my own comment, it blends with the other lines that have concocted descriptions, thus, camouflaging my descriptions that I want other testers to see easily. Having unnecessary descriptionsbloats (a weelittle bit at a time) files that have to be checked in to source control. So the idea in baxatob's community postis great and would meet my needs. A variation of this idea would be an all-time option to enable or disable. If it is enabled, you could press an option to blank outconcocteddescriptions in all lines of the current test after it has been recorded (excluding lines that have already been manually edited, which is already being tagged as in the keyword test file asDescriptionEdited="True"). (One might say I should use Comments to do what I am wanting. However,I use "Comments" to introduce a section of operations, and Description to giveexplanation on a specific line of code as needed. So, I use both Comments and Description) (Note: This idea pertains only to Keyword Testing, not converting a Keyword Test to a script, which does have a mechanism to strip out Description.)Add QT 6 support
Please add QT 6 support. Our company has been using TestComplete for a decade for testing our QT application. We have been updating QT along the way and now need to to update QT 6 so we need to TestComplete to also update their support. We have thousands of man hours of work into our scripts at this point and having to switch to a different software would be a painful experience and would take likely years to get us back to where we are now. QT is a major player in Desktop Testing so I don't think they are going away anytime soon.Update Testcomplete to support more recent browsers
Testcomplete is really far behind on browser support. Edge : 83 - 105 // Current version 112 Chrome 105 // Current version 113 Firefox 91 //Current version 102 More and more tests are starting to break, the community page is full of people with browser problems. It just really needs to get updated to at least 1 or 2 versions ago. I understand that keeping up with the newest version is difficult because of the constant updates. But it's time to support more recent versions again.
Add the PCoIP protocol to the Network Suite / Distributed Testing
It would be great to add the PCoIP protocol as a connection possibility to the Network Suite/Distributed Testing. At the moment only connection options with RDP are available. Benefits of which i could think of: - Support of certain ressource analysis/monitoring tools - More "realistic" setup, as the VM would be connected over a view broker/server (though probably there won'tbe any large difference in performance for example) The only way to make this work until now (that I know of) is to open a session with a zero client and set the connection type in the Network Suite to "Manual", but then obviously all VM's need to run from a physical client.
