Extended clarifications

camaraproject · Dec 4, 2024 · 9f05b73 · 9f05b73
1 parent a1bee21
commit 9f05b73
Show file tree

Hide file tree

Showing 2 changed files with 17 additions and 16 deletions.
diff --git a/artifacts/testing/C01-device-errors.feature b/artifacts/testing/C01-device-errors.feature
@@ -3,15 +3,16 @@ Feature: CAMARA Common Artifact C01 - Test scenarios for device errors
     Common error scenarios for POST operations with device as input either in the request
     body or implied from the access.
 
-    Artifact parameters (to be replaced by values according to the API operation):
-
-    - {{feature_identifier}} 
-
-    This is not a complete feature but a collection of scenarios that can be applied
-    with minor modifications to test plans.
+    NOTES: 
+    * This is not a complete feature but a collection of scenarios that can be applied  with minor
+    modifications to test plans. Test plans would have to copy and adapt the scenarios as part of
+    their own feature files, along with other scenarios
 
-    These scenarios assume that other properties not explicitly mentioned in the scenario
+    * These scenarios assume that other properties not explicitly mentioned in the scenario
     are set by default to a valid value. This can be specified in the feature Background.
+
+    * {{feature_identifier}} has to be substituted to the value corresponding to the feature file where
+    these scenarios are included.
 
     # Error scenarios for management of input parameter device
 

diff --git a/artifacts/testing/C02-phoneNumber-errors.feature b/artifacts/testing/C02-phoneNumber-errors.feature
@@ -1,18 +1,18 @@
 Feature: CAMARA Common Artifact C02 - Test scenarios for phoneNumber errors
 
     Common error scenarios for POST operations with phoneNumber as input either in the request
-    body or implied from the access.
-
-    Artifact parameters (to be replaced by values according to the API operation):
+    body or implied from the access
 
-    - {{feature_identifier}} 
-
-    This is not a complete feature but a collection of scenarios that can be applied
-    with minor modifications to test plans.
+    NOTES: 
+    * This is not a complete feature but a collection of scenarios that can be applied  with minor
+    modifications to test plans. Test plans would have to copy and adapt the scenarios as part of
+    their own feature files, along with other scenarios
 
-    These scenarios assume that other properties not explicitly mentioned in the scenario
+    * These scenarios assume that other properties not explicitly mentioned in the scenario
     are set by default to a valid value. This can be specified in the feature Background.
-
+
+    * {{feature_identifier}} has to be substituted to the value corresponding to the feature file where
+    these scenarios are included.
 
     # Error scenarios for management of input parameter phoneNumber