nebsta
Contributor
Joined 10 years ago
User Profile
User Widgets
Contributions
Improvements after renaming/moving Aliases
Given the technical difficulties of implementing the following idea please can we get an interim solution implemented that will, upon renaming or moving of an Alias within the hierarchy: Automatically update the Alias of 'Compare Property' parameters when they are set using Mode = Object Property Automatically update the Alias of stores objects (e.g. DB Table object). In order to capture other occurrences of the Alias within scripts etc, the user is prompted if they wish to open a find/replace, if they choose to it will automatically populate the former Alias name in Find and new Alias name in Replace with options for the scope to be set to: Current open windows Current Project Project Suite4.6KViews2likes3CommentsRe: When is Smartbear going to work seriously on the Feature Requests
tristaanogre I see your point but this kind of feedback is unquantified and may not represent the views of users as a whole. I think there should be more visibility on feature requests e.g. average age, number created vs number resolved, number of requests that have changed status etc. The top two requests both relate to improvements to the NameMappings where AFAIK there is not currently a work around, they have been raised since 1H 2015 and seem to have been put into the 'too hard basket'. Even as the two two ideas - perhaps having only 56 and 58 kudos votes gives the impression that they are not really needed by users but I would guess that the vast majority of TestComplete users have never used the Smartbear Community, let alone reviewed the feature requests section. If there were an alternative way to achieve the feature request ideas easily then I would not be so worried about them but I don't believe there is. I totally appreciate that there is limited dev resources and we shouldn't be encouraging custom workflows within the tool but IMO there are some very valid ideas with high votes that have been around for a long time and are not being considered.2.6KViews1like3CommentsRe: When is Smartbear going to work seriously on the Feature Requests
Yes the Kudos should perhaps be weighed up against ease of implementation, although I don't agree that we should be prioritising free vs paid users differently - it sounds too complicated for potentially no gain.2.6KViews1like0CommentsRe: When is Smartbear going to work seriously on the Feature Requests
Marsha_R wrote: Counting in the list of feature requests, you only have to go through the top 30 before the number of Kudos drops below 10. In those top 30, 11 are selected for development 3 are implemented 6 are open for discussion 11 are new Looks to me like the list is already being worked on "seriously". If an idea can't get at least 10 Kudos, then it's probably not worth the development time to add it. Marsha_R I disagree - it seems that "Selected for Development" just means that the idea is in the Smartbear backlog for TestComplete - it doesn't indicate that it will ever be worked upon in the near future and in fact one of the comments on the second highest rated idea suggests that given the current architecture it cannot be implemented: "According to our development team, the official status of the feature should be "Not in progress". According to the product owner, the feature request would be a great enhancement but based on our current architecture we are unable to implement this yet. Therefore I do not have a definite answer on when name mapping will be refactored." I have to agree with mgroen2 that not much progress is being made on the implementation of feature requests, especially those with the highest ratings which have been around for a long time. If they are not possible then they should not be marked as "Accepted for Development" as this is misleading. We used to get an update in the monthly newsletter on the number of feature requests submitted vs implemented. As I have mentioned before I think this should be brought back to give better visibility and a thorough triage of the current statuses undertaken.2.7KViews1like2CommentsRe: Most Valuable TestComplete feature
tristaanogre that will teach me for not reading the question thoroughly! In that case I guess I would say the NameMapping. Despite the fact that I think there are a few improvements that could be done to make it a lot easier to maintain (e.g. links above) it does a good job of abstracting references to objects in tests to minimise rework required when the UI is changed.3.6KViews1like0CommentsRe: Most Valuable TestComplete feature
Mine would also be the ability to clean NameMapping https://community.smartbear.com/t5/TestComplete-Feature-Requests/Provide-Ability-to-Clean-Alias-and-Mapped-Objects-Not-Used-in/idi-p/101238 or alternatively the ability to find usages from the NameMapping which would make maintaining the NameMappings easier: https://community.smartbear.com/t5/TestComplete-Feature-Requests/Find-Usages-of-Name-Mapping-Objects-Aliases/idi-p/1190973.6KViews0likes0CommentsRe: aqReporter.dll Error
jjessop We managed to work around this (on a desktop application): "By renaming the 'DockingShell' class to 'MainWindow' I could append test steps without the application crashing. This supports the crash dump investigation which suggests that Test Complete is causing heap corruption during its recording process." AlexKaras FYI2KViews1like0CommentsRe: Auto update scripts when Name Mapping items/aliases are renamed
MKozinets TanyaYatskovska if the above comments are accurate then as per the discussion in https://community.smartbear.com/t5/TestComplete-General-Discussions/TestComplete-s-roadmap-including-feature-requests/td-p/135737/page/3 please can this be moved to a more accurate status e.g. postponed?7.4KViews0likes0CommentsRe: TestComplete's roadmap, including feature requests
TanyaYatskovska thanks for your response! Can I suggest that: 1) A review of the statuses of all existing ideas submitted is completed to make it clearer as to priorities and which are being actively considered for development? The rating system is great to give an indication of how popular an idea is but if it's not going to be implemented due to technical limitations then it can perhaps be slightly misleading to go by this alone. There is currently only one idea at the status of 'Postponed' so it sounds like the ideas are in the wrong statuses. 2) The 'Ideas Submitted' and 'Ideas Implemented' figures are added back into the monthly newsletter to give community members a better overview of activity?2.4KViews1like7CommentsAdd the same Project to ProjectSuite TestItems multiple times
I would like to be able to add the same Project to a ProjectSuite's TestItems multiple times each with different subset of Keyword Tests/Scripts selected for that Project. For some background - I have a Project called Common where I handle common functions such as starting and stopping the application.I would like to configure the TestItems within the ProjectSuite to: 1) Run Common.StartApplication 2) Run through the selected tested within all other Projects 3) Run Common.StopApplication Currently it is only possible to add a Project to the ProjectSuite TestItems once and it is only possible to have one configuration for which tests to run within a Project's TestItems.2.2KViews0likes2Comments