Number of Checkpoint required in Log Summary and log Object
I have noticed that sometime test complete script fails to execute complete scripts and log the results with Zero Warnings and Errors reason could be any but result is incomplete execution of script. When we generate and send email through log object we only gets number of Errors and Warnings which are misleading results or numbers. When we go to the details we find that scripts execution is incomplete. I request you to add number of checkpoints validated by scripts in Log summary (I have highlighted the place to show in attached snapshot). Even if number of Errors and Warnings would be Zero and if we don't get the desired number of checkpoints which could also be zero, we can easily identify that scripts fail to complete their execution.Auto Generate PDF Report
It would be very useful to have a feature where the test logs can be automatically generated to PDF files. Essentially, rather than manually generate a PDF report as an export as instructed in Test Complete documentation: https://support.smartbear.com/testcomplete/docs/testing-with/log/working-with/exporting/index.html#pdf have the PDF report generate with a simple "writeLogToPDF" command. Thanks for your consideration!
Improved Keyword Test correction when renaming Aliases
Hello! Whenever an alias is changed in a project's NameMapping file, TestComplete will offer to automatically correct any items in Keyword Tests that use the alias. However, I have found that this feature only works with Test Actions (On-Screen Action, If Object, etc.) and Checkpoints (Property Checkpoint, Region Checkpoint, etc.) Currently, Logging items (Log, Post Screenshot, etc.) and Statements (While Loop, If... Then, Set Variable Value, etc.) do not get updated automatically with this feature. Having this functionality would help greatly reduce errors that result from partial renaming jobs.manual checkpoint in keyword test
I would like to see on option on keyword tests where you can add a manual checkpoint Currently, if the users has successfully logged in I can put in a checkpoint that states "object found" or by write a code snippet code snippet has: Log.Checkpoint("User " + KeywordTests.login.Parameters.login_user + " successfully logged in") I would like to get the option in a log comment - just like it is for the code (Log.Checkpoint)Allow CTRL select to select multiple values in OCR Checkpoint Recognized Text
Allow CTRL select to select multiple values in OCR Checkpoint Recognized Text. As it functions now, can only either select specific values or groups of consecutive values. Would like to be able to select multiple values that aren't consecutive.
Validating text by using "Properties Checkpoint" should not depend on Auto-wait timeout
When validating forms fields labels, and help text (properties ContentText values), the "Properties Checkpoint" is ideal. However, it waits for the Auto-wait timeout when it fails validation. In a large project, for example only 10 errors exist and each have to wait for the global default of 10 seconds, it would be 100 second additional run time where in automation time is of an essence. Ideally the "Properties Checkpoint" should be performed in tow steps: 1. access the object including wait for the time out 2. compare the property value do not wait for the time out Current options: 1. Change the global default time out of 10 seconds to a very low number, and that is not a good idea and still does not go as fast as should be 2. Override individual "Properties Checkpoint" to set a very low value, is difficult to maintain with constant edits, and still does not go as fast as should be 3. Use the "If Object" or "If Then" with "Log Message" it becomes 4 statements rather than the single "Properties Checkpoint", and still the time out appliesFix checkpoint performance degradation issue for KeyWord tests
In a new versions of Testcomplete is disappeared the ability to select JScript language in project. But for several year has a problem that prevents our team from switching to JavaScript ES6. When test run has repeated Property checkpoints, each other assertion consumes more and more time to finish. It reproduces only in KeyWord tests, runned in JavaScript ES6 project with OnStartTest event is activated. In the attachment you can find an archive that will help you reproduce the problem. Execution of KeyWord test for a JScript ES3 project takes 53 seconds. For a JavaScript ES6 project, the same test takes more than two minutes to execute. There is a huge problem for a big projects. We created support Case #00415520 couple years ago, but this problem does not fixed yet in the newest versions. Perhaps the vote as feature request will push SmartBear to solve such a serious problem.
