Check Interdependencies in Path (0062) analysis uses a combination of the existing Test Impact Radar, Deep Impact Analysis and Overtake sequencing analysis checks to do the following:
1. Explodes out all dependent objects for a transport/change (to configurable number of levels)
2. Adds in all objects above the transport objects in the dependency hierarchy
2. Checks to see if any of the exploded out objects are in transports in the path, in the same target as the transport being analysed or in front of the transport being analysed (i.e. not in production yet) – to provide an intersection of the transports/objects between the transport(s) being analysed and other transports in the path.
It is possible to run the Check Interdependencies in Path analyser in three ways:
i) to report on the intersection of transports/objects if the intersecting transports do not have the same value as a Custom Field on the Business Task(s) being analysed
ii) to report on the intersection of transports/objects if the intersecting transports are not in the same Project(s) as the Business Tasks I am analysing
iii) to report on the intersection of transports/objects if the intersecting transports are not in the Business Tasks I am analysing.
ANALYSIS_TYPE: Whether you want to run the Analysis by i) Custom Field, ii) Project or iii) Task
CUSTOM_FIELD: the Custom Field number if you have selected that Analysis type.
LEVELS: Specify the number of levels to go down in object hierarchy.