Champion Level 3My first opinion is that we should get away from using job titles as a comparison because they're different at every workplace and that might not be the best way to delineate TC usage.
That being said, ideally, keyword test functionality would be the same as scripting functionality, but in reality I think that is a huge thing to ask. We do have the opportunity to ask for new or updated features from SmartBear as we each need them. I've used TC at two different companies, from v7 and up and I have seen many new things added to keyword tests, even some that I had voted for!
Where I work, we are continuously having to decide what software features to develop and who works on it when. We have long term plans and short term plans, and all of those can get interrupted if a customer needs a fix. SmartBear is in that same position and I don't think that just saying "make it all work the same" is something we can ask of them. What if they spend months adapting a feature to keyword testing and it turns out that very few people have a use for it? They could have spent that time on a feature that many people use instead, but "make it all work the same" was the plan, so that's what got done.
If there's something particular that you need to have working in a keyword test, I suggest letting SmartBear know on the feature request forum. If others have the same need, they will vote it up and it will get on the list and all of us will benefit.
First of all, I think, it is all a matter of defining the roadmap of TC, combined with pre-defined mechanism which should be applied to all feature requests.
I think this mechanism should be in the form of a matrix or something, containing several parameters and each parameter should be given a value. Imagine the following parameters were defined: 1) amount of work (effort), 2) how many votes got it 3) does it align with TC's roadmap (which is/should be defined), 4) Do we need to implement this for KDT or scripting, or both? And if both how much effort would it take to align these?
Of course I realize it's a huge think to ask, but on the other hand almost everything you can do with scripting can be done with KDT as well. But, not all. And, I think it's good to share ideas, and to be ambitious. TestComplete is a very broad product it's in the name already. So, with different type of audiences (different usages), there are also different ways to work with TC. And I think all this results in different type of feature requests......
