hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2 Conformance Test Cases for A1-P Producer | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.1 Query policy type test scenarios | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.1.1 Query all policy type identifiers (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.1.1.1 Test description and applicability | The purpose of this test case is to test the query policy types functionality of A1-P Producer as specified in A1AP [4] clause 5.2.3.2. The expected outcome is successful retrieval of policy type identifiers. This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query all policy ty... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.1.1.2 Test entrance criteria | 1) The DUT supports the Query all policy type identifiers procedure. 2) The test simulator has the functionality to initiate A1-P Query all policy type identifiers procedure. 3) A set of policy types (at least two) are supported in the DUT. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.1.1.3 Test methodology | 6.2.1.1.3.1 Initial conditions 1) The DUT has A1-P Producer service ready and available to receive HTTP requests from the test simulator. 2) The DUT supports the three different test configurations listed below to test complete functionality: a) DUT has no policy types available. b) DUT has a single policy type availab... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.1.2 Query single policy type (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.1.2.1 Test description and applicability | This purpose of this test case is to test the query policy type functionality of A1-P Producer as specified in A1AP [4] clause 5.2.3.3. The expected outcome is successful retrieval of the policy type object. This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query single policy ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.1.2.2 Test entrance criteria | 1) The DUT supports the Query single policy type procedure. 2) The test simulator has the functionality to initiate A1-P Query single policy type procedure. 3) A known set of policy types are supported in the DUT. 4) The policy type identifier used for this test is known in advance and used in test simulator to formula... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.1.2.3 Test methodology | 6.2.1.2.3.1 Initial conditions 1) The DUT has A1-P Producer service ready and available to receive HTTP requests from the test simulator. 2) The DUT has the policy types available. 6.2.1.2.3.2 Procedure Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clau... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.1.3 Query single policy type (negative case) - policyTypeId not supported | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.1.3.1 Test description and applicability | This purpose of this test case is to test the query policy type functionality of A1-P Producer as specified in A1AP [4] clause 5.2.3.3. The expected outcome is failure due to policyTypeId not being supported. This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query single policy... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.1.3.2 Test entrance criteria | The test entrance criteria specified in clause 6.2.1.2.2 applies, except that the agreed policyTypeId is NOT available in DUT. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.1.3.3 Test methodology | 6.2.1.3.3.1 Initial conditions The initial conditions specified in clause 6.2.1.2.3.1 applies. 6.2.1.3.3.2 Procedure Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.2.3 containing the unsupported policyTypeId and with empty message body. Step 2. ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.2 Create policy test scenarios | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.2.1 Create single policy (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.2.1.1 Test description and applicability | This purpose of this test case is to test the create policy functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.3. The expected outcome is successful creation of the policy. This test case is conditionally mandatory if the DUT claims to support A1-P service. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.2.1.2 Test entrance criteria | 1) The DUT supports the A1-P Create single policy procedure. ETSI ETSI TS 103 989 V4.2.0 (2025-05) 46 2) The test simulator has the functionality to initiate A1-P Create single policy procedure. 3) DUT and the test simulator have agreed on a policy type to use for this test. 4) The policyTypeId and the JSON schemas of ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.2.1.3 Test methodology | 6.2.2.1.3.1 Initial conditions 1) The DUT has A1-P Producer service ready and available to receive HTTP requests from the test simulator. 2) No policy exists in the DUT for the agreed policy type with the same policyId that will be used by the test simulator. 6.2.2.1.3.2 Procedure Step 1. Send an HTTP PUT request from ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.2.2 Create policy (negative case) - schema validation failure | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.2.2.1 Test description and applicability | This purpose of this test case is to test the create policy functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.3. The expected outcome is failure due to schema validation failure. This test case is conditionally mandatory if the DUT claims to support A1-P service. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.2.2.2 Test entrance criteria | The test entrance criteria specified in clause 6.2.6.1.2 applies. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.2.2.3 Test methodology | 6.2.2.2.3.1 Initial conditions The initial conditions specified in clause 6.2.6.1.3.1 applies. 6.2.2.2.3.2 Procedure Step 1. Send an HTTP PUT request from test simulator to DUT with the correct URI as specified in A1AP [4] clause 6.2.3 and a message body containing the PolicyObject in JSON format. A spelling mistake sh... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.2.3 Create policy (negative case) - policyTypeId not supported | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.2.3.1 Test description and applicability | This purpose of this test case is to test the create policy functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.3. The expected outcome is failure due to policyTypeId not being supported. This test case is conditionally mandatory if the DUT claims to support A1-P service. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.2.3.2 Test entrance criteria | The test entrance criteria specified in clause 6.2.6.1.2 applies except that the agreed policyTypeId is NOT available in DUT. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.2.3.3 Test methodology | 6.2.2.3.3.1 Initial conditions The initial conditions specified in clause 6.2.6.1.3.1 applies. 6.2.2.3.3.2 Procedure Step 1. Send an HTTP PUT request from test simulator to DUT with the incorrect URI, i.e. containing the not supported policyTypeId, and a message body containing the PolicyObject in JSON format. Step 2. ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3 Query policy test scenarios | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.1 Query all policy identifiers (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.1.1 Test description and applicability | The purpose of this test case is to test the query policies functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.2. The expected outcome is successful retrieval of policy identifiers. This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query all policy identifiers... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.1.2 Test entrance criteria | 1) The DUT supports Query all policy identifiers procedure. 2) The test simulator has the functionality to initiate A1-P Query all policy identifiers procedure. 3) The DUT and the test simulator have agreed on a policy type to use for this test. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.1.3 Test methodology | 6.2.3.1.3.1 Initial conditions 1) The DUT has A1-P Producer service ready and available to receive HTTP requests from the test simulator. 2) The DUT supports the three different test configurations listed below to test complete functionality: a) DUT has no policies available for the agreed policy type. b) DUT has a sin... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.2 Query all policy identifiers (negative case) - policyTypeId not supported | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.2.1 Test description and applicability | The purpose of this test case is to test the query policies functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.2. The expected outcome is failure due to policyTypeId not being supported. This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query all policy identi... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.2.2 Test entrance criteria | The test entrance criteria specified in clause 6.2.3.1.2 applies, except that the agreed policyTypeId is NOT available in DUT. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.2.3 Test methodology | 6.2.3.2.3.1 Initial conditions 1) The DUT has A1-P Producer service ready and available to receive HTTP requests from the test simulator. 6.2.3.2.3.2 Procedure Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.2.3 and empty message body. Step 2. At... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.3 Query single policy (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.3.1 Test description and applicability | The purpose of this test case is to test the query policy functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.5. The expected outcome is successful retrieval of policy object. This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query single policy procedure. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.3.2 Test entrance criteria | 1) A policy exists in the DUT and test simulator is aware of the policyTypeId and policyId. 2) The DUT supports the Query single policy procedure. 3) The test simulator has the functionality to initiate A1-P Query single policy procedure. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.3.3 Test methodology | 6.2.3.3.3.1 Initial conditions 1) The DUT supports the Query single policy procedure. 2) The test simulator has the functionality to initiate A1-P Query single policy procedure. 6.2.3.3.3.2 Procedure Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.4 Query single policy (negative case) - policy does not exist | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.4.1 Test description and applicability | The purpose of this test case is to test the query policy functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.5. The expected outcome is failure due to policy being non-existent. This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query single policy procedure. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.4.2 Test entrance criteria | 1) The DUT supports Query single policy procedure. 2) The test simulator has the functionality to initiate A1-P Query single policy procedure. 3) test simulator is aware of the policyTypeId and policyId to use for which no policy exists in the DUT. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.4.3 Test methodology | 6.2.3.4.3.1 Initial conditions 1) The DUT has A1-P Producer service ready and available to receive HTTP requests from the test simulator. 6.2.3.4.3.2 Procedure Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.2.3 and empty message body. Step 2. At... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.5 Query policy status (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.5.1 Test description and applicability | The purpose of this test case is to test the query policy status functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.7. The expected outcome is successful retrieval of policy status object. This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query policy status p... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.5.2 Test entrance criteria | 1) The DUT supports the Query policy status procedure. 2) The test simulator has the functionality to initiate A1-P Query policy status procedure. 3) A policy exists in the DUT and the policyTypeId and policyId is known to the test simulator. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.5.3 Test methodology | 6.2.3.5.3.1 Initial conditions 1) The DUT has A1-P Producer service ready and available to receive HTTP requests from the test simulator. 6.2.3.5.3.2 Procedure Step 1. Send an HTTP GET request from test simulator to DUT with the correct URI format as specified in in A1AP [4] clause 6.2.3 and empty message body. Step 2.... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.6 Query policy status (negative case) - policy does not exist | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.6.1 Test description and applicability | The purpose of this test case is to test the query policy status functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.7. The expected outcome is failure due to policy being non-existent. This test case is conditionally mandatory if the DUT claims to support A1-P service and the Query policy status proce... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.6.2 Test entrance criteria | 1) The DUT supports Query policy status procedure. 2) The test simulator has the functionality to initiate A1-P Query policy status procedure. 3) Test simulator is aware of the policyTypeId and policyId to use for which no policy exists in the DUT. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.3.6.3 Test methodology | 6.2.3.6.3.1 Initial conditions 1) The DUT has A1-P Producer service ready and available to receive HTTP requests from the test simulator. 2) No policy exists for the policyTypeId and policyId that will be used by the test simulator. 6.2.3.6.3.2 Procedure Step 1. Send an HTTP GET request from test simulator to DUT with ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.4 Update policy test scenarios | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.4.1 Update single policy (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.4.1.1 Test description and applicability | The purpose of this test case is to test the update policy functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.4. The expected outcome is successful update of the policy. This test case is conditionally mandatory if the DUT claims to support A1-P service and the Update single policy procedure. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.4.1.2 Test entrance criteria | 1) The DUT supports the Update single policy procedure. 2) The test simulator has the functionality to initiate A1-P Update single policy procedure. 3) A policy exists in the DUT and the policyTypeId and policyId is known to the test simulator. 4) Policy type identifiers used for this test are known in advance and used... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.4.1.3 Test methodology | 6.2.4.1.3.1 Initial conditions 1) The DUT has A1-P Producer service ready and available to receive HTTP request from the test simulator. 6.2.4.1.3.2 Procedure Step 1. Send an HTTP PUT request from test simulator to DUT with the correct URI as specified in A1AP [4] clause 6.2.3 and message body containing the PolicyObje... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.4.2 Update single policy (negative case) - schema validation failure | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.4.2.1 Test description and applicability | The purpose of this test case is to test the update policy functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.4. The expected outcome is failure due to schema validation failure. This test case is conditionally mandatory if the DUT claims to support A1-P service and the Update single policy procedure. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.4.2.2 Test entrance criteria | The test entrance criteria specified in clause 6.2.6.1.2 applies. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.4.2.3 Test methodology | 6.2.4.2.3.1 Initial conditions The initial conditions specified in clause 6.2.4.1.3.1 applies. 6.2.4.2.3.2 Procedure Step 1. Send an HTTP PUT request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.2.3 and a message body containing the PolicyObject in JSON format. A spelling mis... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.5 Delete policy test scenarios | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.5.1 Delete single policy (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.5.1.1 Test description and applicability | This purpose of this test case is to test the delete policy functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.6. The expected outcome is successful deletion of the policy. This test case is conditionally mandatory if the DUT claims to support A1-P service. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.5.1.2 Test entrance criteria | 1) The DUT supports the Delete policy procedure. 2) The test simulator has the functionality to initiate Delete policy procedure. 3) A policy exists in the DUT and the policyTypeId and policyId is known to the test simulator. ETSI ETSI TS 103 989 V4.2.0 (2025-05) 54 |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.5.1.3 Test methodology | 6.2.5.1.3.1 Initial conditions 1) The DUT has A1-P Producer service ready and available to receive HTTP requests from the test simulator. 6.2.5.1.3.2 Procedure Step 1. Send an HTTP DELETE request from test simulator to DUT with the correct URI format as specified in A1AP [4] clause 6.2.3. Step 2. At the test simulator ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.5.2 Delete single policy (negative case) - policy does not exist | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.5.2.1 Test description and applicability | This purpose of this test case is to test the delete policy functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.6. The expected outcome is failure due to policy being non-existent. This test case is conditionally mandatory if the DUT claims to support A1-P service. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.5.2.2 Test entrance criteria | 1) The DUT supports the Delete single procedure. 2) The test simulator has the functionality to initiate Delete single policy procedure. 3) Test simulator is aware of the policyTypeId and policyId to use for which no policy exists in the DUT. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.5.2.3 Test methodology | 6.2.5.2.3.1 Initial conditions 1) DUT has A1-P Producer service ready and available to receive HTTP requests from the test simulator. 2) No policy exists in DUT for the policyTypeId and policyId that will be used by the test simulator. 6.2.5.2.3.2 Procedure Step 1. Send an HTTP DELETE request from test simulator to DUT... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.6 Notify policy status test scenarios | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.6.1 Notify policy status (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.6.1.1 Test description and applicability | This purpose of this test case is to test the policy status notification functionality of A1-P Producer as specified in A1AP [4] clause 5.2.4.8. The expected outcome is successful request for policy status. This test case is conditionally mandatory if the DUT claims to support A1-P service and supports the Notify polic... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.6.1.2 Test entrance criteria | The test entrance criteria for Create single policy specified in clause 6.2.2.1.2 applies. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.2.6.1.3 Test methodology | 6.2.6.1.3.1 Initial conditions The initial conditions for Create single policy specified in clause 6.2.2.1.3.1 applies. 6.2.6.1.3.2 Procedure Step 1. Same as for Create single policy, see clause 6.2.2.1.3.2, including the notificationDestination query parameter. Step 2. At the test simulator the received HTTP response ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3 Conformance test cases for A1-EI Consumer | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.1 Query EI types test scenarios | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.1.1 Query EI type identifiers (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.1.1.1 Test description and applicability | The purpose of this test case is to test query EI type identifiers functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.3.2. The expected outcome is successful validation of the Query EI type identifiers request. This test case is conditionally mandatory if the DUT claims to support A1-EI service and the... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.1.1.2 Test entrance criteria | 1) The DUT has functionality to initiate A1-EI Query EI type identifiers procedure. 2) The test simulator supports the Query EI type identifiers procedure. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.1.1.3 Test methodology | 6.3.1.1.3.1 Initial conditions 1) The test simulator has A1-EI Producer service ready and available to receive HTTP requests from the DUT. 6.3.1.1.3.2 Procedure Step 1. Initiate appropriate action in the DUT to initiate Query EI type identifiers request. Step 2. At the test simulator the contents of the received HTTP r... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.1.2.2 Test entrance criteria | 1) The DUT has the functionality to initiate A1-P Query EI type procedure. 2) A known set of EI types are supported in the test simulator. ETSI ETSI TS 103 989 V4.2.0 (2025-05) 57 3) The EI type identifier used for this test is known in advance and available in DUT to send the Query EI type request for the correspondin... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.1.2.3 Test methodology | 6.3.1.2.3.1 Initial conditions 1) The test simulator has A1-EI Producer service ready and available to receive HTTP requests from the DUT. 2) The test simulator has EI types available. 6.3.1.2.3.2 Procedure Step 1. Initiate appropriate action in the DUT to initiate Query EI type request with a known eiTypeId. Step 2. A... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.2 Create EI job test scenarios | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.2.1 Create EI job (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.2.1.1 Test description and applicability | This purpose of this test case is to test the create EI job functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.4.3. The expected outcome is successful validation of the EI job creation request. This test case is conditionally mandatory if the DUT claims to support A1-EI service. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.2.1.2 Test entrance criteria | 1) The DUT and the test simulator have agreed on an EI type to use for this test. 2) The eiTypeId and the JSON schemas of the EI type used for this test are available and used in DUT to formulate the Create EI job request, and in test simulator to validate the request. 3) The DUT has the functionality to initiate A1-EI... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.2.1.3 Test methodology | 6.3.2.1.3.1 Initial conditions 1) The test simulator has A1-EI Producer service ready and available to receive HTTP requests from the DUT. ETSI ETSI TS 103 989 V4.2.0 (2025-05) 58 2) No EI job exists in the test simulator for the agreed EI type with the same eiJobId that will be used by the DUT. NOTE: The DUT is requir... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.3 Query EI jobs test scenarios | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.3.1 Query EI job identifiers for a single EI type (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.3.1.1 Test description and applicability | The purpose of this test case is to test query EI job identifiers functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.4.2. The expected outcome is successful validation of the Query EI job identifiers request querying for a single EI type. This test case is conditionally mandatory if the DUT claims to s... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.3.1.2 Test entrance criteria | 1) The DUT has functionality to initiate A1-EI Query EI job identifiers procedure. 2) An EI type is agreed to be used in this test and the eiTypeId is known in advance. 3) A set of EI jobs (at least two) exist in the test simulator for the agreed EI type. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.3.1.3 Test methodology | 6.3.3.1.3.1 Initial conditions 1) The test simulator has A1-EI Producer service ready and available to receive HTTP requests from the DUT. 2) The test simulator has EI jobs available for the agreed EI type. ETSI ETSI TS 103 989 V4.2.0 (2025-05) 59 6.3.3.1.3.2 Procedure Step 1. Initiate appropriate action in the DUT to ... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.3.2 Query EI job identifiers for all EI types (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.3.2.1 Test description and applicability | The purpose of this test case is to test query EI job identifiers functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.4.2. The expected outcome is successful validation of the Query EI job identifiers request querying for all EI types. This test case is conditionally mandatory if the DUT claims to suppo... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.3.2.2 Test entrance criteria | 1) The DUT has functionality to initiate A1-EI Query EI job identifiers procedure. 2) The test simulator supports at least one EI type. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.3.2.3 Test methodology | 6.3.3.2.3.1 Initial conditions 1) The test simulator has A1-EI Producer service ready and available to receive HTTP requests from the DUT. 2) One or more EI jobs exist in the test simulator for each EI type supported. 6.3.3.2.3.2 Procedure Step 1. Initiate appropriate action in the DUT to initiate Query EI job identifi... |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.3.3 Query EI job (positive case) | |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.3.3.1 Test description and applicability | The purpose of this test case is to test query EI job functionality of A1-EI Consumer as specified in A1AP [4] clause 5.3.4.5 The expected outcome is successful validation of the Query EI job request. This test case is conditionally mandatory if the DUT claims to support A1-EI service and the Query EI job procedure. |
dc221df23507f299408b696fb47d3ed6 | 103 989 | 6.3.3.3.2 Test entrance criteria | 1) The DUT has functionality to initiate A1-EI Query EI job procedure. 2) An EI job exists in test simulator and DUT is aware of the eiJobId. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.