Showing ideas with status Implemented.
Show all ideas
Status:
Implemented
Submitted on
06-17-2015
10:35 AM
Submitted by
william_roe
on
06-17-2015
10:35 AM
In our trial and error approach to learning TC we have found ourselves with excess baggage (unused mapped objects and Aliases) which we wish to clean up. At some point we disabled 'Map object names automatically' and have a mix of tests using Mapped and Aliased object. The ability to removed mapped objects and aliases which are used in keyword and script tests would be highly benificial. Here isa thread which discusses in further detail. Thanks for your consideration.
... View more
This can be useful in naming objects and in custom logging. Right now the user has to find some way to record it separately, but TestComplete already knows this name so it should be easy to expose.
... View more
Status:
Implemented
Submitted on
04-01-2015
06:11 AM
Submitted by
simon_glet
on
04-01-2015
06:11 AM
Hi, A Name Mapping file is an xml file but its content is difficult to understand and impossible to merge. The current structure forces teams working on the same project to dedicate one personne only to edit the Name Mapping file. Once the editing is done, other members of the project must overwrite their local file. The must be a better way to keep the Name Mapping file in synch. Thanks Simon Glet
... View more
Status:
Implemented
Submitted on
05-08-2015
11:25 AM
Submitted by
joseph_michaud
on
05-08-2015
11:25 AM

In the same fashion that you can select and then run a test item or test item group while viewing the project in TestComplete, it would similarly be useful to be able to select a project test item or test item group and run it with the TestComplete or TestExecute using the command line. So if the project items look like this:
So we might run some tests like this:
TestExecute.exe TestProject14.pjs /run /project:TestProject14 /projectitem: Group1
TestExecute.exe TestProject14.pjs /run /project:TestProject14 /projectitem: ProjectTestItem2
TestExecute.exe TestProject14.pjs /run /project:TestProject14 /projectitem: Group2
Perhaps overloading the /projectitem flag is not a good idea? Then use a new flag, say, ... "/item".
TestExecute.exe TestProject14.pjs /run /project:TestProject14 /item: Group1
TestExecute.exe TestProject14.pjs /run /project:TestProject14 /item: ProjectTestItem2
TestExecute.exe TestProject14.pjs /run /project:TestProject14 /item: Group2
Should we honor or disregard the Enabled selection for the items and groups in the project? Or perhaps honor it by default, and force execution if a "/force" flag is used? For example, where TestItem2 is not enabled:
TestExecute.exe TestProject14.pjs /run /project:TestProject14 /item: ProjectTestItem2 /force
... View more
In order to be able to effectively maintain the Name Mapping & Aliases it would be useful to be able to right click an object in the Name Mapping/Aliases hierarchy and 'Find Usages' which will then bring up a dialog to show all Scripts & Keyword test files that contain references to that object. You can then double click the file in the dialog to take you to the first reference in the file.
... View more
See more ideas labeled with:
I like the BDD principles and was investigating it's potential application combined with TestComplete.
Read this, this, this and this article on it.
Personally I have come to the conclusion that BDD has definitely potential but the frameworks currently investigated (Lettuce, Cucumber) require way to much fragile configuration (settings project folders name, test names, etc, etc) to be able to use this effectively in Contiuous Delivery / Continuous Integration alike approaches. In practise you end up maintaining the configuration files, editing connection / integration scripts to keep 'alive' the integration between Cucumber/Lettuce and TestComplete.
Therefore, I would go for a BDD framework within TestComplete (or another product from SmartBear) which can guaranty integrity of BDD features/specifications/test-steps on the one hand, and the actual tests/validations (wheter these are scripts or Keyword tests) on the other hand.
I would like to see this implemented in either TestComplete itself (sort of like currently Manual Testing (and the conversion to automated tests) is supported (but this is going to be depreciated unfortunately but that's another subject), or in a seperate tool which would then be required to be very well integrated with TC (such as like sharing variables, parameters, etc).
When supported in TestComplete itself it could be placed in "advanced node" in a project, for example. And this module would be able to read (import) .feature files like the GIVEN/WHEN/THEN , Gherkin language support. After importing the test/QA engineer would do his/her work to 'knot' the features and the tests together in the framework.
By keeping this all in one tool would prevent ending up in constantly updating settings like updating configuration files, (re)define directories if projects are moved, etc. That's exactly what's NOT needed in CI/CD environments.
... View more
In an application that has modules that are laid out the same but have different names, this would save the user from having to map each one.
... View more
Status:
Implemented
Submitted on
03-15-2016
02:49 AM
Submitted by
Manfred_F
on
03-15-2016
02:49 AM
If a script causes an error, TC will either terminate the test run or just go on, depending on the "stop on error" option. In both cases, trying to find the cause of the error is very time consuming: You have to re-run the test and set a breakpoint there. I'd propose a "break on error" option, which behaves as if I had set a breakpoint in the errorneous line. TC shall execute the line, monitor the error, and give me the chance to work with the debugger: evaluate expressions, re-run statements and so on
... View more
I've requested the option turn this off completely, but if that does not happen, I'm suggesting an improvement to the functionality: Currently there is some logic that will remove the closing quote/bracket in certain situations, but not in one particular situation where I strongly believe it should. When I type a quote or bracket immediately preceding or following existing alpha or numeric text, I am almost always correcting something I did not code perfectly in the first place. What currently happens is I try to insert a single quote before some text that's already in place, and I get two quotes and have to remove one (once I notice it), and again when I move to the end of the existing text to add the closing quote. I am quite frequently having to delete these auto-inserted closing marks. So, my suggestion is to not insert the closing quote/bracket when the cursor position is immediately before or immediately at the end of alpha or numeric text.
... View more
Hi all, 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. Notes: 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? :D) 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. Then: - 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
... View more
When right-click on the project or Project Suite, the menu is displayed.
Would be great if the option to open the location of the project (or project suite) using Windows File Explorer would be added to this menu . Just like it is implemented in Visual Studio.
... View more
I would like to see TestComplete releases in 64 bit mode. Since more and more applications are becoming 64bit and (Virtual, Cloud) Operating Systems as well. Also OS'es are moving toward 64-bit. And with access to more memory, more scalability etc, I propose to release TestComplete in a native 64-bit variant.
While also keep releasing 32bit versions as well.
... View more
Status:
Implemented
Submitted on
05-15-2017
06:18 AM
Submitted by
Jean-Daniel
on
05-15-2017
06:18 AM
Hi, It would be nice if Testcomplete could recognise "Paper-Input" Web elements. Such Web elements should be browsed in the Testcomplete Object Browser as Standard HTML Divs are. This would make the namemapping robust and flexible for Web Tests using this new tehcnology. Thanks Jean-Daniel
... View more
It would be useful for me if TestComplete supported labeling (or categories) for tests. Most of my tests are regression, however some are security/permissions tests. The permissions tests are long running and I would like to clearly identify them as such using a label or category. It could then be possible to run all tests with a particular label or category in a project that would usually be disabled on a standard test run.
... View more
Status:
Implemented
Submitted on
08-06-2015
06:13 AM
Submitted by
anonymous_67424
on
08-06-2015
06:13 AM
In stead of implementing numerous "Generate Screenshot" in my Keyword tests, I would like have ability to start video capturing and end video capturing. Save it in the testlog, also saving possible as avi / mpeg4 (up to the tester to decide). Optional include parameters in the videorecording on screen: name of current test, variable names, etc. Would be very welcome!
... View more
Check out the video attached. Leave your cursor at the end of a line and in a few seconds the entire script highlights. According to Vladimir, this is not a bug but a feature. According to the information from the R&D team this is done to calculate an identifier under the cursor and cannot be disabled. The developer knows about this behavior and confirms this is planned one. But it highlights the ENTIRE SCRIPT. I'm calling "Shenanigans" on the Programmer here. This is extremely annoying when i'm trying to track down some code. I've put up with this for years and am still not liking it. At least allow us to change the highlighting options.
... View more
Status:
Implemented
Submitted on
01-10-2018
01:52 PM
Submitted by
Christophe
on
01-10-2018
01:52 PM
Hi, I suggest that TestComplete supports Google Polymer framework. Thanks in advance.
... View more