As stated in this feature request, we work agile and the tester gets new applications versions (almost) on a daily basis.
The tester does not know which objects have been changed/deleted. And does ...
Montikore, Colin_McCrae Thank you both for the useful comments.
I want to emphazise that the world around us tester is changing rapidly and agile and even CI/ CD affects the way we can do our work (as testers), whether we like it or not. (of course I would like to have much more time to build a profound testing framework including greate namemapping features and all), do some great engineering with it, etc... but can't do it in current situations.
Please don't expect that this feature request will solve all the problems in Agile/CI/CD driven projects.
No project is the same. So much variables, so much influencing factors... its's all about complexity of the AUT, chosen development approach(es), (internal) commitments, people, etc, etc, etc....
It's just that I think TestComplete should become better at supporting CI/CD driven projects, and I think it has real good potential considering the changes in software/development world in the (near) future.
I know that Tricentis (Tosca) is working on similar scan / update "namemapping model" on their to-be-released updated version of Tosca as well. Tosca is not a perfect product nor Tricentis is a perfect company far from that but by evaluating their product I saw something interesting, and I translated this to TestComplete and I saw something was missing.