WARNING! Gitlab maintenance operation scheduled for Monday, 20 April between 12:00 and 14:00 (CET). During this time window, short service interruptions (less than 5 minutes) may occur. Thank you in advance for your understanding.
@@ -22,6 +22,14 @@ POST Alarm - Method not implemented
Integerresponse status405
Get information about a configuration
[Documentation]Test ID: 7.4.3.1
...Test title: Get information about an alarm
...Test objective: The objective is to read an individual alarm.
...Pre-conditions: The related alarm exists
...Reference: section 7.4.3 - SOL002 v2.4.1
...Config ID: Config_prod_VNFM
...Applicability:
...Post-Conditions:
LogQuery VNF The GET method queries information about an alarm.
Set Headers{"Accept":"${ACCEPT}"}
Set Headers{"Content-Type": "${CONTENT_TYPE}"}
@@ -47,7 +55,14 @@ PUT Alarm - Method not implemented
Integerresponse status405
PATCH Alarm
[Documentation]This method modifies an individual alarm resource
[Documentation]Test ID: 7.4.3.2
...Test title: Modify an individual alarm resource
...Test objective: The objective is to Modify an individual alarm resource
...Pre-conditions: The related alarm exists
...Reference: section 7.4.3 - SOL002 v2.4.1
...Config ID: Config_prod_VNFM
...Applicability:
...Post-Conditions:
logTrying to perform a PATCH. This method modifies an individual alarm resource
Set Headers{"Accept":"${ACCEPT}"}
Set Headers{"Content-Type": "${CONTENT_TYPE_PATCH}"}
@@ -65,10 +80,14 @@ PATCH Alarm
LogValidation OK
PATCH Alarm - Conflict
[Documentation]Conflict
...The operation cannot be executed currently, due to a conflict with the state of the �Individual alarm� resource.
...Typically, this is due to the fact that the alarm is already in the state that is requested to be set (such as trying to acknowledge an already-acknowledged alarm).
...The response body shall contain a ProblemDetails structure, in which the �detail� attribute should convey more information about the error.
[Documentation]Test ID: 7.4.3.2-1
...Test title: Modify an individual alarm resource - Conflict
...Test objective: The objective is to Modify an individual alarm resource
...Pre-conditions: The related alarm exists
...Reference: section 7.4.3 - SOL002 v2.4.1
...Config ID: Config_prod_VNFM
...Applicability:
...Post-Conditions: The alarm resource is not modified
Depends On TestPATCH Alarm# If the previous test scceeded, it means that the alarm is in ackownledged state
logTrying to perform a PATCH. This method modifies an individual alarm resource
Set Headers{"Accept":"${ACCEPT}"}
@@ -84,10 +103,14 @@ PATCH Alarm - Conflict
LogValidation OK
PATCH Alarm - Precondition failed
[Documentation]Precondition Failed
...A precondition given in an HTTP request header is not fulfilled. Typically, this is due to an ETag mismatch,
...indicating that the resource was modified by another entity. The response body should contain a ProblemDetails structure,
...in which the �detail� attribute should convey more information about the error.
[Documentation]Test ID: 7.4.3.2-1
...Test title: Modify an individual alarm resource - Precondition failed
...Test objective: The objective is to Modify an individual alarm resource
...Pre-conditions: The related alarm exists
...Reference: section 7.4.3 - SOL002 v2.4.1
...Config ID: Config_prod_VNFM
...Applicability:
...Post-Conditions: The alarm resource is not modified
Depends On TestPATCH Alarm# If the previous test scceeded, it means that Etag has been modified
logTrying to perform a PATCH. This method modifies an individual alarm resource