Hello All,
I am trying to understand the Service Test Management API and its possible implementation in two use-case scenarios Customer Experience assurance & Planned/proactive test. Is there a call flow or a sequence diagram that explains the big picture with end-to-end invocation sequence of these APIs.
It is not coming out clearly the use of two resources serviceTestSpecification resource and serviceTest resource with mostly the same information of metrics, threshold rules and consequences in both of them.
Since the serviceTest resource has a state, it looks to be an active resource which would be instantiated when the scenario is invoked with one or more serviceTestSpecifications. Is serviceTestSpecification like a template associated with each service? When will serviceTestSpecification resource be created? Will there be a serviceTestSpecification resource when the service is added to catalog or service instance is added to the inventory?
If there are more than one instances of the same service, will there be one serviceTest resource testing the service quality for all or one serviceTest resource per service instance.
Will there be a list of metric resource associated with each service that the user invoking the serviceTest can pick from?
Why is captureFrequency and captureMethod part of TestMeasureDefinition? Shouldn't this be same for all metrics within a ServiceTestSpecification?
What is the purpose of Purpose of thresholdRuleSeverity? How different levels of thresholdRuleSeverity trigger different consequences when consequence resource is a part of thresholdRule? Will there be multiple thresholdRules one for each severity and if the Rule has both lower and upper comparators, they will be ANDed.
Thanks
Abha Gupta