I wanted to suggest a feature where-in we could compare Keyword Tests without its xml structure but its actual Keyword content . This really helps the engineers to refer old project files and see the changes and most of all it helps the integrator to understand the changes gone through .
More like a beyond compare tool where-in you can even make changes if required.
everytime you open a keywordtest the project tree jumps to its location. if you have many many items in your tree it can be really annoying because you have to scroll and scroll. would be nice to have an option to disable the automatic behavior and use manual expansion (if needed).
In TC 8, opening a failed test run's log was fast even if the log was very large. The reason it was fast was because TC 8 only loaded into memory enough of the test run's log to populate the Log Items panel and the Project Log panel, e.g. a few seconds at most. I would then use the Log Items panel to drill down to the test item I'm interested in, which again is fast because I'm usually interested in the last test item as that's the one containing the error that caused the test run to fail. And loading that test item was also fairly fast (a few seconds at most) because only one log file was being load, i.e. that of the test item in question.
So in TC 8 I could get to the test run's failure point pretty quickly, i.e. less than 30 seconds.
However in TC 12, if the log contains one or more errors (and they nearly allows do because who looks at successful test runs), after opening the log TC12 automatically sets focus to the first error in the test run log. This can be very slow if the log is large, e.g. this often takes 5 minutes, and this approach seems to require TC to load the test run's complete set of log files into memory, which explains the slowness.
So how about TC having an additional checkbox in TC's Options->Engines->Log page that can be used to enable/disable the automatic setting of focus to the first error in a log when opening a log. The default would be for the checkbox to be enabled, as per current TC 12 functionality.
For my company's usage I would typically set the option to disabled, so it behaves more like TC 8.
I imagine the code change to honor this option would be small.
I expect the existing TC code does something like this:
So my feature request would change it to:
, i.e. a relatively small change.
I'd like to be able to open up another project and just view the tests that are in it. Right now I have to switch projects to do that or take up another license and neither one of those are very convenient.
I am refferring to this post.
Currently, the tester (QA user), Test Automation Framework designer needs to write code to create validations on database tables, if he/she uses WHERE clausule.
Database Table Checkpoints, as currently implemented, do not support dynamically populated values in the "WHERE" clausules.
I would like to see TestComplete improved so that the Database Table Checkpoint feature supports dynamically populated "WHERE" SQL statements.
I have created 100s of variables over the last couple of years and have no way of knowing if they are now redundant / where I am using them
It would be useful to be able to see a list of variables that are not used in any tests and to see a list of tests that variables are used in.
Currently the command line option "ExportLog" allows the user to export either mht or the proprietary .tcLogX format of TC/TE per the help:
"/ExportLog:File_name (or /el:File_name) - Commands TestExecute to export test results to an .MHT or .tcLogX file specified by the File_name parameter after the test run is over.
Important: File_name should specify the name of a non-existent file. If it specifies an existing file, TestExecute will fail to run the test.
It is recommended that File_name specify the fully-qualified file name. If the parameter value does not include the folder path, TestExecute saves the file to the current working folder (by default, it is the project folder)."
However, Chrome does not support .mht files (and surprisingly it is not easy to add support, I have tried. I swore there would have to be a good plugin to do this) and of course tcLogX is not easily viewable unless through TC (another feature request for Smartbear to create a simple tcLogX viewer app? )
In script you can use the Log.SaveResultsAs to save to html easy enough and put this line in the Engine stop event.
My request is to simply allow access to the html option of Log.SaveResultsAs through the "ExportLog" commandline option.
- Any browers can read the file easily
- I can export the html to an intranet web server and easily share the results with other staff internally
<Method="myMethod" Routine="myMethod">This is a method <Parameter1Type>string</Parameter1Type> <Parameter2Type>integer</Parameter2Type> </Method>
You can zoom in on the Picture/Image comparison windows but often I need to zoom in on a specific section where a comparison failed. There is currently no way to "box zoom" where you select a section of the image and zoom straight to it.
Sometimes there are very small differences that I have to zoom in on and it's tedious to use the general zoom and then grab/slide over to where the small difference is.
Below is an example of how it is now. Not too bad but when it's a very small difference it's very tedious to zoom in on a dozen pixels. When I select a box with the current tool, ideally there would be a context menu to zoom to the selection. Or else when you release the box selection it would auto-zoom as happens in tools in the Adobe suite.
I'd imagine this would be very trivial for a dev to implement.
My Test Complete execution normally takes more than a Hour or so. Hence in the Indicator popup if we have the timer which will display the HH : MM : SS running.
This will help us to know approx. when it will end or knowing other stuffs wrt timings.
I'm expecting something like below,
When you click on the error message cell in the above table, it navigates back to the keyword/script line.
It would be nice if you can click on the object name in the screen shot and navigate back to the Object Browser
In the same fashion that we can use the GUI to enable/disable extensions, it would be nice to be able to choose which extensions are active when TestComplete starts up.
/EnableExtension:[AllCommon | AllDesktop | AllWeb | AllMobile | extensionName]*[:force][:verbose]
/DisableExtension:[AllCommon | AllDesktop | AllWeb | AllMobile | extensionName]*[:force][:verbose]
- The enable/disable settings will be saved (just as if we had used the GUI to make the changes).
- Multiple flags are processed in order.
This can be used as a method for preventing the need for certain licenses. For example, if you have only a few Web licenses, you can use a command line which always disables the Web extensions, and then use a different command line which enables the Web extensions.
Please make it possible to resize "Edit Objects" window: full screen, custom size, minimize.
It is very difficult to edit complicated objects with big number of nodes, when you are not able to resize the standard window.
It's a pain internally for our team that when we introduced new parameter to an existing keyword tests, all tests that are reference to it are failing. Often times, the new parameters are added for some particular tests and not for all the tests.
We would like the existing tests to adapt the new parameter and just default it to whatever the default value is set to that parameter. That way the existing tests won't fail and we don't have to change every tests that are reference to that test with new parameter. We have daily CI automated tests and the # of tests are getting bigger. In the long term, this will be very hard to maintain and prevent us from making a change like this as it messes up everything.
Our developers have upgraded through the newer versions of Delphi (now on 10.1.2 Berlin).
They have started to make use of the Themes available in these newer versions.
Unfortunately, Test Complete does not seem to work to well on applications compiled to include these Themes.
It would be helpful if Test Complete could accommodate working with them.
During Script development, when we call a function from one to another(using Code Completion), if the calling function has parameters then that should be displayed in the current function as we have option in the Eclipse.