For instance, I set up a dependency expression, such as
My expectation was that as soon as MasterTest1 entered a DOWN state that the dependent test(s) would launch. Instead it waits for the dependent tests next scheduled run. I'm sure that an argument can be made for it being this way, but it's a bit backwards as I see it.'%::MasterTest1::SimpleStatus%' =='DOWN'
Suggestion: Wouldn't it make sense to turn this around and define a test's dependents instead of it's Masters?
Then a change in the master tests status could execute the appropriate action on the array of it's dependents. You could even define a dendency based on a folder name and the entire folder's tests would be dependent by inheritance, and any new tests added would be included. Especially handy with the classic router dependency scenario.
This also avoids the inevitable confusion if the master test is deleted or it's name is changed. Can you tell me what happens to a dependency expression if one of the master tests used in the expression is deleted or the name changes?
Which begs for an HML auditting tool, especially for Enterprise licenses, to determine if there are any 'orphan' expressions, variables, profiles, etc.
The equivalent of a Windows 'Registry Fix' tool. Better yet, have HM actively audit/validate changes whenever one is posted, or before saving the changes back to file.
And I'm admittedly lazy, so how about an expression builder for dependency expressions? I'm a keyboard klutz and fail to put the approprate quotes or double colons in the right place
