TestComplete Feature Requests

Given this ability to determine test complete behavior on error:   I would like to differentiate a runtime error as with an error in test creation and a test failure or checkpoint error. Something similar to many unit test frameworks assert fail so that I can have different playback behavior   and a failure specific event   ... View more

I would like to see TestExecute integrated into TestComplete so that a user can control the TestExecute instance to run nominated test cases directly from the TestComplete Project. It would be nice to be able to nominate where test cases will be run i.e. whether to run on the current machine under TestComplete or run on a nominated PC (on the network) using the TestExecute application and license attached to the remote PC. Ideally the user would be able to nominate at an individual test case level where to execute the test with the TestComplete PC being the default option. However, even the ability to nominate entire projects to be tested under TestExecute on a remote PC from the Project Suite Test Items list would be beneficial. The expectation being that the results are captured under a consolidated Project Suite log file for analysis.   This is fairly high level but happy to discuss further. ... View more

Use a different format than *.MHT for the result logs when test cases are executed using TestAdapter in the Azure pipelines and Azure Test Plans. ... View more

A good to have feature would be if the Log report summary can include a logo of your respective company. Branding is important to many organizations and we see this as an advantage when the PDF can be shared with a specific logo.  ... View more

Instead of limiting the number of logs kept by Test Complete by a count,  it would be nice if it they could be limited by a time period. For example, keep the last Month of test logs.   This would be useful for users who run a high volume of tests in a short amount of time, but would still like to keep their output logs under control and accessible. ... View more

When we have a project that integrates to Cucumber, we have the option to have TestComplete push results to Cucumber during a test run.   The process of pushing results seems to be somewhat fragile (as any REST API interaction is), with timeout errors etc every once in a while. Any kind of error whilst pushing to Cucumber is logged as a RED ERROR that cannot be intercepted (even if intercepted, TestComplete logs the error anyway).   If we use CI/CD to run our tests, pushing to Cucumber errors will halt the CI/CD process (since there is an error in the logs). However, just because pushing the results to Cucumber has failed, doesn't mean that the test run itself was a fail. Our CI/CD process should be able to continue (depending on project configuration).   I am suggesting an option somewhere in the project to set whether any Cucumber pushing error should be displayed as an ERROR or a WARNING. This way we could set the project to throw a WARNING, if the pushing to cucumber fails, instead of an error. Then, if that was the only thing that went wrong, the CI/CD process could continue. ... View more

Currently there it is just logged with what exe & version & parameters passed. From past experience it would be good to have following details logged too: Configured session details - Run interactive user session flag - Use active session flag - Session screen resolution (sample 2560x1440) The real facts from the Session Desktop during test execution - Is it an interactive user session? - Is an already active session used or did the test runner created a new one? - Session screen resolution (sample 1679x551 which does not match the requested one see above) ... View more

While the new sharing results options are quite handy, for an enterprise scenario the 2-week window is too less. An option for unlimited time would be needed. Please consider increasing the time limit duration.   Also, the share option saves company information in the Smartbear server. We need an option that will save the log locally without the smartbear URL.  ... View more

Azure DevOps seems to be a popular option these days. Please consider adding the following as a feature in the near future.   1. Post Bugs from Test complete to Azure DevOps 2. Post Work Item from TestComplete to Azure DevOps 3. Upload Test Plan from TestComplete to ADO.  ... View more

Log files can take up lots of space on a HDD   You have the option to limit the number of log files kept, but this is not always the answer you are looking for   The logs could be stored in another location possibly a network location which will save resources on the local computer (would store locally if location not available - drive offline)     ... View more

When I check logs, I always have to: enlarge the block with the screenshot to immediately see which elements are in action expand the test case tree on the left to see which test case we are checking at the moment. I suppose that other users also suffer from such inconveniences, and maybe they have other wishes to view the logs. That's why I think it should be possible to adjust the display once and keep it. So that you don't have to change the display of the log window every time you run test cases.   ... View more

Hi, It would be very useful to get instant test logs during test execution. Currently TestComplete does not provide a scripting interface to the test log of the current run. it is very limiting for us. We have desktop UI tests with several hours execution and waiting for the log result is very impractical. I think it would be nice to support for example Elasticsearch live logging like many other modern test frameworks, not only HTML reporting that is very outdated today. ... View more

Good to Include Screenshot in the summary log report as an evidence report This helps the readability of the execution It can be extracted and share the results to the manual team It acts a TC document which can be used an KT document for the new joiners It acts as a proof for raising a bug incase of failure       ... View more

Please provide ability to develop Testcomplete tests using VS Code (dll). No need to include namemapping or object spy feature. Just create an extension for quick test script development and execution using TestExecute. ... View more

Please have an alternative to read mht file, because of the end of life of Internet Explorer.  Also change the default report type from Azure DevOps. The default report type is now mht which it cannot be used from June 15 2022. ... View more

Hey, it would be great if the log would not display the whole screen from 3 monitors which are in use. Better would be that TestComplete checks where the tested application runs and just make screenshots for the log from this monitor - or implement an option to choose which monitor should be logged.   Attached is a screenshot from a log with 3 monitors. ... View more

The screenshots in the Log files on the file directory would be much more useful outside of Test Complete if you could specify the filename when the screenshot is taken. Ideally, you would be able to specify the filenames always, but at least it should be an option to specify the filename of a screenshot when one uses the Post Screenshot Operation. ... View more

Hi there, we have a scenario where a single script decides which tests run and then runs the tests. This causes all logs to have the same name: Script Test Log [ScriptUnit\scriptName]   It would be great if this script could rename the log items.   More information: http://community.smartbear.com/t5/Getting-Started-with/Rename-test-logs/m-p/116832   Greetings, vat ... View more

When executing test cases in Test Complete or Test Execute via the command line, you can specify which folder to write the test results to but CAN NOT specificy Zephyr Folder. Please add support for Test Complete/Test Execute to write results to Zephyr Folders via command line (or other executions)  ... View more