Script Tagging for Impact of Code Changes

Hello,

I was wondering if we could get some sort of recommendation from your team on how we could create something to understand the impact on our scripts based upon impacts of a specific function or screen.

For example, if we have a test case called ITP_ManualPick (Interplant Transfer Order with Manual Picking), we might know that the following screens are most likely impacted.

1. Web - Orders
2. Web - Appointment Search
3. Web - Appointment Schedule
4. Mobile - Manual Pick
5. Mobile - Job Pool

It would be essential for us to understand what scripts may be impacted based upon changes made to a certain screen or function within our application. For example, if Orders screen was impacted, we could get a list of scripts that are 'tagged' somehow with being related to this application function/screen. This not only allows us to not have to 'guess' what scripts may need updating, but this also would allow us to get an adequate list of scripts that should be ran based upon certain code deploys. If Appointment Search, and Appointment Schedule screens have recent code changes, we could run ALL scripts that have the relative tag onto it.

I know we could maybe use keywords on a test suite level, but I wasn't sure if there are any plans to make it easier to do this behavior within the application down the road?

To give a bit more insight, we have about 40 scripts for this specific application currently, and we will be drastically adding onto this. By the end of September, we will have probably 65, and by end of this fiscal year near 90-100. Again, this is just for one application, this is not including all of the other applications we are focused on. :)