avl123
New Contributor
Joined 5 years ago
User Profile
User Widgets
Contributions
Adding support to Qt Q*View controls e.g. QTreeView, QListView, QTableView...
We happened to have those everywhere throughout our Qt application. The contents of these controls can't be accessed in the test leading to the workarounds like clicking based on coordinates and verifying through image compare, which is not robust and increases the dependency to the environment as well as to any cosmetic changes in UI. The excitement of the development about the idea of substituting all View controls with corresponding Widget controls only because of the limitations of the testing software is not particularly high.Re: Allow OOP coding with full intellisense in Testcomplete
This is my pain too and I am happy to see that I am not alone. There are a number of other ideas addressing missing functionality of TC Editor compared to any decent IDE. An ultimate solution as for me is to enable possibility to work in an external IDE unlocking all the power it can offer. I have ended up using VS Code + this tool here https://github.com/deitry/testcomplete-ts-api to develop in JavaScript. As long as I don't need debugging I just run TestExecute to execute the script from the command line within VS Code. I can also halfway use typescript to define types and apply typing with jsdoc syntax which TC treats as a comment I guess. It is so much more efficient to work in a proper IDE with all the additional tools you can install in it!577Views0likes0CommentsUI object as an argument for a function
Hi, I have a JavaScript function performing operations on the UI object which is its argument. The functioned is called like this: myFunction(Aliases.Parent.Object). Recently I started getting an error during test run from time to time: The tested window (or control) has been deleted. Details: This error occurred when the tested window (or control) or its parent object was deleted or recreated right before the method call. For example, you stored a window reference to a variable and then called a method through this variable. If the object has been recreated, then to avoid the error, get the new object before the method call. So now I have an additional function: function getObject(){return Aliases.Parent.Object} and the initial function is called like this: myFunction(getObject()). I guess it should solve the problem, but I wonder if it is the best/correct way of doing it? Should Aliases generally be avoided as arguments?Solved831Views0likes2Comments