...
Error Scenario | Expected behavior | Sign-off | |
|---|---|---|---|
| 1 | Non responding DMIs (configurable timeout) | An error message listing the 'pending' CM Handle IDs. statusMessage/statusCode to be agreed. | |
| 2 | Non Existing or non-valid CM Handle Ids | An error message listing the 'rejected' CM Handle IDs. | |
| 3 | DMI Plugin without CM Event subscription support | An error message listing the 'rejected' CM Handle IDs | |
| 4 | Late Response (after timeout defined in #1) from DMI | A list of outcomes (complete status on how many cmhandles are pending/rejected/accepted) from client subscription is returned in response. statusMessage/statusCode to be agreed. |
|
| 5 | Create for existing subscription id | The whole subscription will be rejected. statusMessage/statusCode to be agreed. |
|
| 6 | Delete for non-existing subscription id | The whole delete subscription will be rejected. statusMessage/statusCode to be agreed. |
|
| 7 | Error upon error | An error scenario on a second subscription for the same cm-handle/xpath as a previous subscription which did not complete successfully (yet) to be discussed, see Error Upon Error Combinations |
...
...
Characteristics
Parameter | Expectation | Notes | Sign-off | |
|---|---|---|---|---|
| 1 | Frequency of LCM Subscription Events | No high volume of such events is expected For testing purpose 1 LCM event per minute would suffice. | kieran mccarthy confirmed |
|
| 2 | Number of Subscriptions | Max: 200 | kieran mccarthy confirmed | |
| 3 | CM Handles per Subscription | Avg: 200 Max: 500 (document only) | kieran mccarthy to confirm | |
| 4 | Xpaths per Cm Handle | Avg: 10 | ||
| 5 | Status update processing time | (Order of 30) seconds (NCMP side) |
...