.NET Core 8 Support
Hi, I wanted to ask when .NET assemblies with .NET Core and .NET 8.0 applications will be supported. https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core Because the versions currently supported by TC are officially outdated and are no longer supported. Thanks and best regardsOCR Recognize DetectTable enhancements
// Specify the preferable search area var searchPref = spLargest; var table = OCR.Recognize(Grid).DetectTable(searchPref, hasHeader); I have above code, and depending on what is configured in the searchPref variabele, it detects or leaves out certain columns for the same Grid. I feel it's not that robust. 1st NF: perhaps some preview window could be opened to actually see at which columns it looks when using DetectTable, because now you don't have such an overview and you hope for the best and try different options, spLargest etc... 2nd NF: Behaviour like the Table Checkpoint wizard. In the Table Checkpoint wizard you could drag and specify your table area to let OCR take a look at and pull data from non-supported grids/tables. So you can be more specific than the standard DetectTable functionality.
onLogError Event handler should handle Freeze Diagnostics Error
If an error is logged as a result of the Freeze Diagnostics this should be handled by the onLogError event handler so the user can add code to set how the test reacts to the freeze. Currently this is not handled(confirmed by smartbear support) which makes the Freeze Diagnostic tool almost useless since the user cannot program the test to react to the freeze. The test just ends, which basically no different than if the freeze diagnostic is off. This is very similar to the process crashed message also ignores the event handler. https://community.smartbear.com/idea/testxcompletefeaturerequests/onlogerror-event-handler-should-handle-process-crashed-message/233461 Really all errors should go through event handler or else it just become this guessing game of when it will and when it won't work...even if the issues are documented as they are with the crash error.Project suite - Global recordings
Consider the following scenario: -A base solution, created with various recording that can be re-used by other solutions. Let's take an example, Login recording for example. -A solution C, which has a project that already uses some reference recordings, like the Login Recording from the base solution. When you create another project in solution C and want to re-use the already referenced Login Recording of the project that was there initially, for the new test plan of the newly created project this is not possible when you drag and try to drop the Login recording into the new test plan. TestComplete wouldn't allow it. Now you have to add reference the same Login recording from the base solution again in your new project, whilst it is already referenced in the project that was there before. Hence you have now two times the same recording from the base solution referenced for different projects in your solution. I would go for something like project suite referenced recordings, which are only referenced one time, and can be re-used by different projects/testplans in your solution without the need to add the same recording each time for every project in your solution. Another scenario: One solution with various projects which consists of recordings. You create a new project called B in this solution and want to re-use a recording from an existing project. Then you have add a reference to a recording from another project in the same solution. This is cumbersome.Global Items in TestComplete
Every project has his Stores, NameMapping, TestedApps etc in a Project Suite project scoped. My idea is, that if you have a common objects that can be re-used by multiple projects, recordings, name mapping objects, instead of having to re-import them for every project in your suite, you have the option to also have them globally on Project Suite Level, to be then shared over the various projects instead of each project having to it's own version of Name Mapping, Tested Applications and such. Example: Project A -> user recordings, namemapping from base solution Project B --> user recordings, namemapping from base solution What it is today and what it could be: If you use global namemapping, user recording that your projects digest, then you only have to update/modify them in one place, instead of all your projects. I do would have the option still to have project scoped, namemapping, recordings etc next to the globally ones.Script tests - Show in Name Mapping Editor/Show in Object Browser
With a Keyword test, you have the availability in the right-click context menu: Show In Name Mapping Editor or Show In Object Browser for an UI-item. In Script tests however, these right click menu options are not available for UI-items.
Need Headless option for uploading the file from File explorer by clicking upload button in the UI.
By clicking upload button in the UI, it will open the file explorer and by giving the path of the file and select the file and click open via headless mode should be required. Kindly look into it and provide the valid solution.Referenced recordings overview
In TestComplete, you can reference recording/import recordings from other solution. Would be handy to have some mechanism in place where you have an overview from which solution these referenced recordings originate from. Currently only the option, show in file explorer is shown.
Add support for testing in multiple instances of the same desktop app
According to the support team there is currently no way to test in multiple instances of the same application. For example, consider a test where you launch multiple instances of Visual Studio and start debugging an application in each instance. If you try to record this test, it records all the operations as if there is once instance of Visual Studio - there is no way to differentiate between them. So when you play the test back, it chooses one instance and tries to execute all operations in that one instance, which fails. In order to automate this test case you would need to be able to specify "In instance 0, do this" and "In instance 1, do that".
