Issue Description:
Below mentioned test cases are failing :
OAMLAYER / BASICPART / ACTION-PROFILE / CAPABILITY/OPERATION-NAME / GET / CONTINUOUS INTEGRATION / REQUEST NOTIFIED? - 4 REQUESTS IN THE FOLDER
OAMLAYER / BASICPART / ACTION-PROFILE / CAPABILITY/LABEL / GET / CONTINUOUS INTEGRATION / REQUEST NOTIFIED? - 4 REQUESTS IN THE FOLDER
OAMLAYER / BASICPART / ACTION-PROFILE / CAPABILITY/DISPLAY-IN-NEW-BROWSER-WINDOW / GET / CONTINUOUS INTEGRATION / REQUEST NOTIFIED? - 4 REQUESTS IN THE FOLDER
OAMLAYER / BASICPART / ACTION-PROFILE / CONFIGURATION/CONSEQUENT-OPERATION-REFERENCE / GET / CONTINUOUS INTEGRATION / REQUEST NOTIFIED? - 4 REQUESTS IN THE FOLDER
OAMLAYER / BASICPART / ACTION-PROFILE / CONFIGURATION/CONSEQUENT-OPERATION-REFERENCE / GET / CONTINUOUS INTEGRATION / REQUEST NOTIFIED? - 4 REQUESTS IN THE FOLDER
OAMLAYER / BASICPART / RESPONSE-PROFILE / CAPABILITY/OPERATION-NAME / GET / CONTINUOUS INTEGRATION / REQUEST NOTIFIED? - 4 REQUESTS IN THE FOLDER
OAMLAYER / BASICPART / RESPONSE-PROFILE / CAPABILITY/FIELD-NAME / GET / CONTINUOUS INTEGRATION / REQUEST NOTIFIED? - 4 REQUESTS IN THE FOLDER
OAMLAYER / BASICPART / RESPONSE-PROFILE / CAPABILITY/DESCRIPTION / GET / CONTINUOUS INTEGRATION / REQUEST NOTIFIED? - 4 REQUESTS IN THE FOLDER
OAMLAYER / BASICPART / RESPONSE-PROFILE / CAPABILITY/DATATYPE / GET / CONTINUOUS INTEGRATION / REQUEST NOTIFIED? - 4 REQUESTS IN THE FOLDER
OAMLAYER / BASICPART / RESPONSE-PROFILE / CONFIGURATION/VALUE / GET / CONTINUOUS INTEGRATION / REQUEST NOTIFIED? - 4 REQUESTS IN THE FOLDER
Root cause :
As , part of above request while executing the OamLog/v1/list-records-of-application is failing with 401 unauthorized since Operation key is not provided.
Solution:
In the test-suite to fetch the operation key for /v1/list-records-of-applicatioon,
We will fetch OamLog reference core model control construct , search for the op-s of /v1/list-records-of-application and fetch operation-key from the found op-s.
But , in the current test suite the operation key is being fetched from the action-profile instead of operation-server.
Issue Description:
Below mentioned test cases are failing :
OAMLAYER / BASICPART / ACTION-PROFILE / CAPABILITY/OPERATION-NAME / GET / CONTINUOUS INTEGRATION / REQUEST NOTIFIED? - 4 REQUESTS IN THE FOLDER
OAMLAYER / BASICPART / ACTION-PROFILE / CAPABILITY/LABEL / GET / CONTINUOUS INTEGRATION / REQUEST NOTIFIED? - 4 REQUESTS IN THE FOLDER
OAMLAYER / BASICPART / ACTION-PROFILE / CAPABILITY/DISPLAY-IN-NEW-BROWSER-WINDOW / GET / CONTINUOUS INTEGRATION / REQUEST NOTIFIED? - 4 REQUESTS IN THE FOLDER
OAMLAYER / BASICPART / ACTION-PROFILE / CONFIGURATION/CONSEQUENT-OPERATION-REFERENCE / GET / CONTINUOUS INTEGRATION / REQUEST NOTIFIED? - 4 REQUESTS IN THE FOLDER
OAMLAYER / BASICPART / ACTION-PROFILE / CONFIGURATION/CONSEQUENT-OPERATION-REFERENCE / GET / CONTINUOUS INTEGRATION / REQUEST NOTIFIED? - 4 REQUESTS IN THE FOLDER
OAMLAYER / BASICPART / RESPONSE-PROFILE / CAPABILITY/OPERATION-NAME / GET / CONTINUOUS INTEGRATION / REQUEST NOTIFIED? - 4 REQUESTS IN THE FOLDER
OAMLAYER / BASICPART / RESPONSE-PROFILE / CAPABILITY/FIELD-NAME / GET / CONTINUOUS INTEGRATION / REQUEST NOTIFIED? - 4 REQUESTS IN THE FOLDER
OAMLAYER / BASICPART / RESPONSE-PROFILE / CAPABILITY/DESCRIPTION / GET / CONTINUOUS INTEGRATION / REQUEST NOTIFIED? - 4 REQUESTS IN THE FOLDER
OAMLAYER / BASICPART / RESPONSE-PROFILE / CAPABILITY/DATATYPE / GET / CONTINUOUS INTEGRATION / REQUEST NOTIFIED? - 4 REQUESTS IN THE FOLDER
OAMLAYER / BASICPART / RESPONSE-PROFILE / CONFIGURATION/VALUE / GET / CONTINUOUS INTEGRATION / REQUEST NOTIFIED? - 4 REQUESTS IN THE FOLDER
Root cause :
As , part of above request while executing the OamLog/v1/list-records-of-application is failing with 401 unauthorized since Operation key is not provided.
Solution:
In the test-suite to fetch the operation key for /v1/list-records-of-applicatioon,
We will fetch OamLog reference core model control construct , search for the op-s of /v1/list-records-of-application and fetch operation-key from the found op-s.
But , in the current test suite the operation key is being fetched from the action-profile instead of operation-server.