From 242f46b99839424ad8fb42ed9dd422404d8bd438 Mon Sep 17 00:00:00 2001
From: Pelayo Torres <pelayo.torresalonso@telefonica.com>
Date: Tue, 11 Feb 2025 09:52:03 +0100
Subject: [PATCH] Fix of events test cases 7 and 8
---
doc/testing/testplan/api_events_service/README.md | 14 ++++++--------
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/doc/testing/testplan/api_events_service/README.md b/doc/testing/testplan/api_events_service/README.md
index 6ecb183..ee86bc3 100644
--- a/doc/testing/testplan/api_events_service/README.md
+++ b/doc/testing/testplan/api_events_service/README.md
@@ -353,7 +353,7 @@ At this documentation you will have all information and related files and exampl
1. Register provider and publish one API at CCF
2. Register Invoker and Onboard Invoker at CCF
3. Discover published APIs and extract apiIds and apiNames
- 4. Subscribe to **SERVICE_API_AVAILABLE** and **SERVICE_API_UNAVAILABLE** event filtering by aefId. Enhanced_event_report active at supported features.
+ 4. Subscribe to **SERVICE_API_AVAILABLE** and **SERVICE_API_UNAVAILABLE** event. Enhanced_event_report active at supported features.
5. Retrieve {subscriberId} and {subscriptionId} from Location Header
6. Provider publish new API.
7. Provider remove published API.
@@ -373,12 +373,11 @@ At this documentation you will have all information and related files and exampl
* Get **Api Ids** And **Api Names** from response.
- 5. Event Subscription to SERVICE_API_AVAILABLE and SERVICE_API_UNAVAILABLE of provider previously registered:
+ 5. Event Subscription to SERVICE_API_AVAILABLE and SERVICE_API_UNAVAILABLE:
1. Send **POST** to **https://{CAPIF_HOSTNAME}/capif-events/v1/{subscriberId}/subscriptions**
2. body [event subscription request body] with:
1. events: **['SERVICE_API_AVAILABLE','SERVICE_API_UNAVAILABLE']**
- 2. eventFilter: only receive events from provider's aefId.
- 3. supportedFeatures: binary 0100 -> string **4**
+ 2. supportedFeatures: binary 0100 -> string **4**
3. Use **Invoker Certificate**
6. Publish new Service API at CCF:
@@ -429,7 +428,7 @@ At this documentation you will have all information and related files and exampl
1. Register Provider and publish one API at CCF
2. Register Invoker and Onboard Invoker at CCF
3. Discover published APIs and extract apiIds and apiNames
- 4. Subscribe to **SERVICE_API_UPDATE** event filtering by aefId. Enhanced_event_report active at supported features.
+ 4. Subscribe to **SERVICE_API_UPDATE** event. Enhanced_event_report active at supported features.
5. Retrieve {subscriberId} and {subscriptionId} from Location Header at event subscription
6. Provider update information of Service API Published.
@@ -449,12 +448,11 @@ At this documentation you will have all information and related files and exampl
* Get **Api Ids** And **Api Names** from response.
- 6. Event Subscription to SERVICE_API_UPDATE of provider previously registered:
+ 6. Event Subscription to SERVICE_API_UPDATE:
1. Send **POST** to **https://{CAPIF_HOSTNAME}/capif-events/v1/{subscriberId}/subscriptions**
2. body [event subscription request body] with:
1. events: **['SERVICE_API_UPDATE']**
- 2. eventFilter: only receive events from provider's aefId.
- 3. supportedFeatures: binary 0100 -> string **4**
+ 2. supportedFeatures: binary 0100 -> string **4**
3. Use **Invoker Certificate**
7. Update published API at CCF:
--
GitLab