Skip to content
Snippets Groups Projects
Commit d8376943 authored by Jorge Moratinos's avatar Jorge Moratinos
Browse files

Provider Management refactored2 

!
parent efcf3594
No related branches found
No related tags found
1 merge request!12Resolve "Change order of sections in tests to improve readability"
Hide whitespace changes
Inline Side-by-side
doc/testing/testplan/api_provider_management/README.md
+ 52
− 47
View file @ d8376943
......@@ -13,6 +13,11 @@ At this documentation you will have all information and related files and exampl
* Provider is pre-authorised (has valid certificate from CAPIF Authority)
**Execution Steps**:
1. Create private and public key for provider and each function to register.
2. Register Provider.
**Information of Test**:
1. Create public and private key at provider for provider itself and each function (apf, aef and amf)
......@@ -30,11 +35,6 @@ At this documentation you will have all information and related files and exampl
* Authentication Bearer with access_token
* Store each cert in a file with according name.
**Execution Steps**:
1. Create private and public key for provider and each function to register.
2. Register Provider.
**Expected Result**:
1. Register Provider at Provider Management:
......@@ -45,6 +45,7 @@ At this documentation you will have all information and related files and exampl
2. **apiProvCert** under **regInfo** is set properly
5. Location Header must contain the new resource URL **{apiRoot}/api-provider-management/v1/registrations/{registrationId}**
## Test Case 2: Register Api Provider Already registered
**Test ID**: ***capif_api_provider_management-2***
......@@ -57,6 +58,12 @@ At this documentation you will have all information and related files and exampl
* Api Provider was registered previously and there is a {registerId} for his Api Provider in the DB
**Execution Steps**:
1. Create private and public key for provider and each function to register.
2. Register Provider.
3. Re-Register Provider.
**Information of Test**:
1. Create public and private key at provider for provider itself and each function (apf, aef and amf)
......@@ -78,12 +85,6 @@ At this documentation you will have all information and related files and exampl
* Same regSec than Previous registration
**Execution Steps**:
1. Create private and public key for provider and each function to register.
2. Register Provider.
3. Re-Register Provider.
**Expected Result**:
1. Re-Register Provider:
......@@ -95,6 +96,7 @@ At this documentation you will have all information and related files and exampl
* detail with message "Provider already registered".
* cause with message "Identical provider reg sec".
## Test Case 3: Update Registered Api Provider
**Test ID**: ***capif_api_provider_management-3***
......@@ -107,6 +109,12 @@ At this documentation you will have all information and related files and exampl
* Api Provider was registered previously and there is a {registerId} for his Api Provider in the DB
**Execution Steps**:
1. Create private and public key for provider and each function to register.
2. Register Provider
3. Update Provider
**Information of Test**:
1. Create public and private key at provider for provider itself and each function (apf, aef and amf)
......@@ -129,13 +137,6 @@ At this documentation you will have all information and related files and exampl
* body [provider request body] with apiProvDomInfo set to ROBOT_TESTING_MOD
* Use AMF Certificate.
**Execution Steps**:
1. Create private and public key for provider and each function to register.
2. Register Provider
3. Update Provider
**Expected Result**:
1. Register Provider:
......@@ -162,6 +163,11 @@ At this documentation you will have all information and related files and exampl
* Api Provider was not registered previously
**Execution Steps**:
1. Register Provider at CCF
2. Update Not Registered Provider
**Information of Test**:
1. Create public and private key at provider for provider itself and each function (apf, aef and amf)
......@@ -185,11 +191,6 @@ At this documentation you will have all information and related files and exampl
* body [provider request body]
* Use AMF Certificate.
**Execution Steps**:
1. Register Provider at CCF
2. Update Not Registered Provider
**Expected Result**:
1. Update Not Registered Provider:
......@@ -200,6 +201,7 @@ At this documentation you will have all information and related files and exampl
* detail with message "Not Exist Provider Enrolment Details".
* cause with message "Not found registrations to Send **THIS** api provider details".
## Test Case 5: Partially Update Registered Api Provider
**Test ID**: ***capif_api_provider_management-5***
......@@ -212,6 +214,12 @@ At this documentation you will have all information and related files and exampl
* Api Provider was registered previously and there is a {registerId} for his Api Provider in the DB
**Execution Steps**:
1. Register Provider at CCF
2. Register Provider
3. Partial update provider
**Information of Test**:
1. Create public and private key at provider for provider itself and each function (apf, aef and amf)
......@@ -235,12 +243,6 @@ At this documentation you will have all information and related files and exampl
* body [provider request patch body]
* Use AMF Certificate.
**Execution Steps**:
1. Register Provider at CCF
2. Register Provider
3. Partial update provider
**Expected Result**:
1. Partial update provider at Provider Management:
......@@ -248,6 +250,7 @@ At this documentation you will have all information and related files and exampl
2. body returned must accomplish **APIProviderEnrolmentDetails** data structure, with:
* apiProvDomInfo with "ROBOT_TESTING_MOD"
## Test Case 6: Partially Update Not Registered Api Provider
**Test ID**: ***capif_api_provider_management-6***
......@@ -260,6 +263,12 @@ At this documentation you will have all information and related files and exampl
* Api Provider was not registered previously
**Execution Steps**:
1. Register Provider at CCF
2. Register Provider
3. Partial update provider
**Information of Test**:
1. Create public and private key at provider for provider itself and each function (apf, aef and amf)
......@@ -283,13 +292,6 @@ At this documentation you will have all information and related files and exampl
* body [provider request patch body]
* Use AMF Certificate.
**Execution Steps**:
1. Register Provider at CCF
2. Register Provider
3. Partial update provider
**Expected Result**:
1. Partial update provider:
......@@ -301,6 +303,7 @@ At this documentation you will have all information and related files and exampl
* detail with message "Not Exist Provider Enrolment Details".
* cause with message "Not found registrations to Send **THIS** api provider details".
## Test Case 7: Delete Registered Api Provider
**Test ID**: ***capif_api_provider_management-7***
......@@ -313,6 +316,12 @@ At this documentation you will have all information and related files and exampl
* Api Provider was registered previously
**Execution Steps**:
1. Register Provider at CCF
2. Register Provider
3. Delete Provider
**Information of Test**:
1. Create public and private key at provider for provider itself and each function (apf, aef and amf)
......@@ -335,17 +344,12 @@ At this documentation you will have all information and related files and exampl
* Send **DELETE** **https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations/{registrationId}**
* Use AMF Certificate.
**Execution Steps**:
1. Register Provider at CCF
2. Register Provider
3. Delete Provider
**Expected Result**:
1. Delete Provider:
1. **204 No Content** response.
## Test Case 8: Delete Not Registered Api Provider
**Test ID**: ***capif_api_provider_management-8***
......@@ -358,6 +362,11 @@ At this documentation you will have all information and related files and exampl
* Api Provider was not registered previously
**Execution Steps**:
1. Register Provider at CCF
2. Delete Provider
**Information of Test**:
1. Create public and private key at provider for provider itself and each function (apf, aef and amf)
......@@ -380,11 +389,6 @@ At this documentation you will have all information and related files and exampl
* Send **DELETE** **https://{CAPIF_HOSTNAME}/api-provider-management/v1/registrations/{API_PROVIDER_NOT_REGISTERED}**
* Use AMF Certificate.
**Execution Steps**:
1. Register Provider at CCF
2. Delete Provider
**Expected Result**:
1. Delete Provider:
......@@ -395,6 +399,7 @@ At this documentation you will have all information and related files and exampl
* detail with message "Not Exist Provider Enrolment Details".
* cause with message "Not found registrations to Send **THIS** api provider details".
[provider request body]: ./provider_details_post_example.json "API Provider Enrolment Request"
[provider request patch body]: ./provider_details_enrolment_details_patch_example.json "API Provider Enrolment Patch Request"
......
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment