Apparently you are worried about the efforts required to maintain your tests in case of changes in the Application Under Test (HTML pages). I think the best way to avoid it is: “Don’t look into the detail of HTML elements”.
An alternative approach is available: “visual testing”. I am aware that you, @sumiranraut96 , once asked Katalon TestOps Vision. So I suppose you are aware of what “visual testing” is. In a visual testing you will take screenshots of a web page at least twice; compare them; find any visual difference. As for “visual testing” you would create very little of Test Objects, or maybe even none. Since you create very little Test Objects, the efforts required to maintain the visual testing suite would be small.
I would rather suggest to you, @sumiranraut96, to leave your current test asset as is.
Rather, you should change your mind fresh and look at “visual testing”. Why not you try to build a new set of Visual Testing? If you could build a visual testing suite that fullfill your business requirements, then you can replace significant portion of your current set of tests with the new visual testing. Then you can erase significant portion of your 15K+ Test Objects. A strategic withdrawal.
Another “Visual Testing” tool : Applitool
I find this article is nice to read to understand the “Visual Testing” concept.
A few weeks ago there was a post
This told me of a company ‘Eggplant Software’. I think there project is a sort of “visual testing” tool. They claim their product is widely used, easy, fast, AI-driven, … more and more. You might be interested in it.
There is another Visual Testing tool named Percy: