From 991f0c3d31e2b09cc826f926577d0bf637a019cf Mon Sep 17 00:00:00 2001 From: Eric Murray Date: Thu, 9 Apr 2026 15:20:24 +0100 Subject: [PATCH] Fix type in @DeviceIdentifier_retrieveIdentifier_200.05_success_scenario_2-legged_token_after_SIM_card_swap --- .../device-identifier-retrieveIdentifier.feature | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/code/Test_definitions/device-identifier-retrieveIdentifier.feature b/code/Test_definitions/device-identifier-retrieveIdentifier.feature index 48ea3b5..5cca7e5 100644 --- a/code/Test_definitions/device-identifier-retrieveIdentifier.feature +++ b/code/Test_definitions/device-identifier-retrieveIdentifier.feature @@ -110,7 +110,7 @@ Feature: Camara Mobile Device Identifer API, vwip - Operation: retrieveIdentifie @DeviceIdentifier_retrieveIdentifier_200.05_success_scenario_2-legged_token_after_SIM_card_swap Scenario: Retrieve device identifier for DEVICE1 with SIM card SIMCARD2 using 2-legged access token - Given SIMCARD1 is installed within DEVICE1, which is connected to the network + Given SIMCARD2 is installed within DEVICE1, which is connected to the network And no subject is identified by the access token And request property "$.device.phoneNumber" is set to PHONENUMBER2 When the HTTPS "POST" request is sent