Values from previous Textbox disappears when it's time to input the date value
Hello there! I'm working with TestComplete on an Electron-based Desktop application. I'm getting an issue where trying to create a form for a product (which requires NAME, TYPE, DESCRIPTION, START DATE, END DATE as inputs) is not filling up correctly when running the Keyword Test.This means that running the Keyword Test (or the script test translated from the Keyword Test) doesn't mimic the actual user-actions that I just recorded (although the screenshots from the Test Visualizer shows that all of the values are being inputted fine). Filling up the first 3 inputs (NAME, TYPE, DESCRIPTION) are done with no issues, but when it comes to auto filling up the START DATE, the values from the first 3 inputs disappear as the value for the START DATE is inputted (specifically when it's time to enter the year - just entering the month or day doesn't make the other values disappear). When using Object Spy, I notice that just having the month and day for the DATE values doesn't register the value, such that the outerHTML displays <input id="startDate" type="date" value="">, which could be the reason why it doesn't delete the first 3 values. However, adding the year (even just the first digit) removes the first 3 values on the texboxes. So having the START DATE value as "05/10/2024" gives the outerHTML: <input id="startDate" type="date" value="2024-05-10"> Note that the input tag (or outerHTML) for the first 3 textboxes is formatted like this initially: <input id="name" value=""> I believe it has something to do with how the first 3 inputs are TextBox Objects and are using the method SetText() while the START/END DATE inputs are a different Object which uses the method Keys(). I attached an image of the script version of the Keyword Test (where "customApp" is just a placeholder). I also attached the image of the form where I enter the information, in which the input for OWNER is also a textbox and should not matter since it's not editable (it's automatically generated). Thank you so much for reading this and I would really appreciate the help!
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.
Change the OS region format all at once
Hi all, is there a way to change the regional setting so that we change the format based on a given format such as French-France ('fr-FR') : I saw that i can use the script to change the SetLocaleInfo to change each properties one by one, but i would prefer to use the Format pre-set settings to tests. Thank you.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.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 for 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.
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".
