On the feature request page you can see a lot of new ideas, feature requests have been added by the all of us community members. I wonder if it would be in any way possible to give some sort of estimation as to how and when some of the features are going to be (or thought of) implemented in future versions of TestComplete? I mean some sort of a roadmap.Personally, I am a fan of transparency and I also hope not only amount of votes (or kudos) will be the one and only criteria for the selection.... (eg I have some features I'd love to see implemented but these seem to be irrelevant to others given they have little to no kudos). PS: TestComplete is a great product of course, and I think by implementing the feature requests done by the community would make TC even better.

I have seen this request /suggestion somewhere before. And answer was “There is a Status for each request” unfortunately “ status” doesn’t make any sense to me as an user. And as far as remember, time frame cannot be expose since it’s subject to change and it’s on the hand of TC internal development team. having said that agree with mgroen2 it's a great product and visibility would make it better.

Probably because, for the most part, the tool is very robust, has a lot of options and possibilities, and is easily usable, already, by a wide variety of skill sets. So, generally speaking, a broader road map isn't as high an interest for a lot of people. The primary concerns for most people doing automated testing are whether or not the tool supports the latest development technologies. TestComplete is doing a pretty good job of staying on top of browser versions, they've already released a feature that allows for cross browser testing that is expandable, the various component libraries are frequently being refreshed and updated as they become more widely used, and so on. So, it's really hard to see what kind of "road map" is necessary beyond what is already in the feature requests part of the forum.

Agree with Robert. Also, considering just released CrossBrowserTesting.com integration, my guess is that improvements and functionality extension will be done in this area. Also I think that some evolutionary improvements can be done in the field of Android / iOS support. And I believe that something from Features Requests will be considered as well.

mgroen2 totally agree with this post! I've been quite active in using the feature request forum - both submitting and giving kudos to posts, however, I find it frustrating that no feedback is given on roughly when we can expect to see these (if ever). Some of my ideas will make the tool so much easier for me to use - especially in regards to maintaining the Name Mappings. I appreciate that TC development requires significant time for supporting new versions of web browsers, new technologies etc, however it really seems like a missed opportunity to not act on these user suggestions. The monthly community journal used to detail "Implemented Ideas" however this seems to have dropped off recently and I noticed that ideas that have been marked as implemented are often done so because the feature already exists. When you start to look at some of ideas in detail I get the impression that "Selected for Development" does not suggest that it is actively being worked on. For example, https://community.smartbear.com/t5/TestComplete-Feature-Requests/Provide-Ability-to-Clean-Alias-and-Mapped-Objects-Not-Used-in/idi-p/101238 is one of the highest rated idea with 54 votes and I think would be an excellent feature. It was moved to "Selected for Development" in March 2016 and I asked for an updated in June but didn't get a reply :(

Hi, Without any intention to start any holy war... :) Just two quick personal comments: 1) > I get the impression that "Selected for Development" does not suggest that it is actively being worked on. I think this should be read as 'Included into Backlog' 2) > Cleaning of Aliases and NameMapping tree: While the request and functionality itself might be useful indeed, I hardly see at the moment how this can be effectively implemented if the tests use some data-driven framework where object aliases are provided from some csv or Excel file and even can be constructed from more than one piece and resolved later via eval() function call. A lot of us use this type of framework and I think that Support will be ready to discuss effective implementation of such use case with anyone who has a good idea. Personally I don't have any good idea at the moment. This is very similar to the question discussed here not long ago when a guy asked if it is possible to get in TestComplete a list of test functions that are not used in test code. And the answer was pretty the same: it is not clear how to handle the case when function name is just mentioned in some configuration file and called than via eval() call...

TestComplete's roadmap, including feature requests

23 Replies

NisHera
Valued Contributor
8 years ago
I have seen this request /suggestion somewhere before. And answer was “There is a Status for each request” unfortunately “ status” doesn’t make any sense to me as an user. And as far as remember, time frame cannot be expose since it’s subject to change and it’s on the hand of TC internal development team.

having said that agree with mgroen2 it's a great product and visibility would make it better.
- mgroen2
  Super Contributor
  8 years ago
  NisHera wrote:
  I have seen this request /suggestion somewhere before. And answer was “There is a Status for each request” unfortunately “ status” doesn’t make any sense to me as an user. And as far as remember, time frame cannot be expose since it’s subject to change and it’s on the hand of TC internal development team.
  
  having said that agree with mgroen2 it's a great product and visibility would make it better.
  NisHera thanks for the feedback. Indeed I remember asking for more 'transparancy' regarding feature request (and their follow up plans)...
  On the feedback page it's announced that 'We need your help' ..let's just hope all the feedback (feature requests) get rewarded somehow, in the near future...!
  - mgroen2
    Super Contributor
    8 years ago
    Anyone?
tristaanogre
Esteemed Contributor
8 years ago
Again, as noted, there are other technological factors at work. Honestly, if I had my druthers, I'd prefer to see TestComplete stay on top of rapidly changing mobIle and Web technologies and maintaining their support of the various application frameworks and components. This, by itself, is a huge effort. Some of the bells and whistles we are asking for, while nice to have, are able to be worked around with script code and other efforts. Not supporting the latest browser version or component library is not something that can be worked around.

While on one level I agree it would be nice to see some movement on those feature requests, they, by no means, are mission critical for doing the work. I'm willing to give SmartBear the leeway to delay implementation so long as they continue to enhance the aforementioned critical things... which they are so I'm fine.
- mgroen2
  Super Contributor
  8 years ago
  tristaanogre wrote:
  Again, as noted, there are other technological factors at work. Honestly, if I had my druthers, I'd prefer to see TestComplete stay on top of rapidly changing mobIle and Web technologies and maintaining their support of the various application frameworks and components. This, by itself, is a huge effort. Some of the bells and whistles we are asking for, while nice to have, are able to be worked around with script code and other efforts. Not supporting the latest browser version or component library is not something that can be worked around.
  
  While on one level I agree it would be nice to see some movement on those feature requests, they, by no means, are mission critical for doing the work. I'm willing to give SmartBear the leeway to delay implementation so long as they continue to enhance the aforementioned critical things... which they are so I'm fine.
  tristaanogre I don't disagree with you. Priority needs to be set, and one of the major things is keep up to date with support of latest technologies.
  However, focus should be more than just that. I mean, there is (I guess) a capable development team with good technical skills working at SmartBear. They should be doing theirs jobs by keeping the product up-to-date. That includes the whole spectrum of product development: supporting of latest technologies, bug fixes, follow up of feature requests as well.
  
  Let me put it this way: what is the point of setting up a forum on which feature requests can be reported, while not having implemented a proper following up procedure? Look at the numbers: approx. 320 feature requests are entered. Implemented are 25, thats a 7,8 percent ratio. And I am talking about a time frame of 2 years...
  
  That's not illustrating an appreciation of the user feedback on the forum.
  
  I (and am sure other active forum members) have put effort in entering useful and realistic product updates in the feature requests section. I would like to see this effort rewarded. And see proper follow up on the entered feature requests.
  - TanyaYatskovska
    SmartBear Alumni (Retired)
    8 years ago
    Hi Team,
    
    First of all, I want to thank you for all the feature requests you submit. We really appreciate it!
    
    We have a team allocated to review the ideas with the highest ratings, and they do this on a regular basis. Some ideas are approved for implementation, others are postponed for various reasons including technical limitations.
    
    The rating system allows us to choose features that you really want to see in TestComplete. So, we focus on the most popular feature requests. If you feel that you submitted an idea that TestComplete really needs, ask other community members to vote it up. Our Team will review it and make a decision.

Forum Discussion

TestComplete's roadmap, including feature requests

23 Replies

Related Content

TestComplete End of Life and Support Roadmap

TestComplete Professional purchase does not include bitbar?

TestComplete with Zephyr Scale

TestComplete with Zephyr Scale

Roadmap of Swagger Codegen - When covering PHP 7+ Client

Recent Discussions

TC15 Log Details shows # of tests with warnings/errors, not TC14's # of warnings/errors

Change the OS region format all at once

Keyword Test - Click - use -1, -1 by default?

Chrome/Edge Extension not always working... why?

Name Mapping Issue